JDBC Driver Is Not Setting SQLWarning When ResultSet Concurrency Has To Be Changed By The RDBMS
Last updated on SEPTEMBER 01, 2014
Applies to:JDBC - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Essentially, if an application calls Connection.createStatement and sets the ResultSet type and concurrency, the RDBMS may change the concurrency subsequently due to some precondition that is not known until the statement is executed. In those cases, it is expected that SQLWarning would be set to a message, but ORACLE JDBC is returning Null instead.
As we can see here the Warnings always are null, even though the Currency has changed and it does not respect what the program is using.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms