|
If you were logged in you would be able to see more operations.
|
|
|
|
Statement + ResultSet setFetchDirection should ignore FETCH_REVERSE and FETCH_UNKNOWN instead of throwing an exception
See also section 13.5 of JDBC 4.2:
"Hints provided to the driver via this interface may be ignored by the driver if they are not appropriate."
|
|
Description
|
Statement + ResultSet setFetchDirection should ignore FETCH_REVERSE and FETCH_UNKNOWN instead of throwing an exception
See also section 13.5 of JDBC 4.2:
"Hints provided to the driver via this interface may be ignored by the driver if they are not appropriate." |
Show » |
|
Improvement
Closed
Major
Statement + ResultSet setFetchDirection should ignore FETCH_REVERSE and FETCH_UNKNOWN instead of throwing an exception
The JDBC spec is a bit ambiguous about it, so setting FETCH_REVERSE and FETCH_UNKNOWN is allowed on a non-scrollable statement, and will be inherited as such by the non-scrollable result set, but setting that same value explicitly on a non-scrollable result set itself is not allowed and will throw an exception. This is similar to what the PostgreSQL JDBC driver does.
We ignore the hint entirely.
As part of this changed, calling get/setFetchDirection on a closed statement or closed result set will always result in an SQLException (this was done inconsistently).