T2 and T4 drivers return different errors if fetch/get data is issued when cursor is after last row

[Aruna Sadashiva]

JDBC T2 and T4 drivers return different errors if we try to fetch rows when cursor is beyond resultset or if resultset is empty.

T2 returns:
Exception...The cursor is after last row, which could be due to the result set containing no rows, or all rows have been retrieved.

T4 returns:
Exception...The message id: invalid_row
org.trafodion.jdbc.t4.HPT4Exception: The message id: invalid_row

Rao thinks this maybe bcoz T2 is not optimized and its still going to server.

[Kevin Xu (kai-hua-xu)]

There is a method TrafT4ResultSet.isBeforeFirst() which allows you get the cursor status, while error 29050 occurs. Since T4 and T2 are different from each other on logic, they may have different errors. I don’t think it’s a good idea to unify the error messages. Currently, T4 has 188 error messages at least while T2 has 89 messages on Java side. By the way, T4 only have source code in Java while T2 contains it in both Java and C++.

[Kevin Xu (kai-hua-xu)]

T4 and T2 are different projects. no need fixes here. will be closed if there is no other comments.

[Aruna Sadashiva (aruna-sadashiva)]

Hi Kevin,

This bug was filed mainly bcoz Rao felt that the t2 code may not be optimized, as mentioned in the description. Was any investigation done to verify and fix this?

Also, both t2/t4 are implementation of jdbc standard, it will be nice if both drivers behaved similarly.

Thanks.
-Aruna

[Aruna Sadashiva (aruna-sadashiva)]

Testcase is attached.