My Oracle Support Banner

JDBC Driver Is Not Setting SQLWarning When ResultSet Concurrency Has To Be Changed By The RDBMS (Doc ID 1668724.1)

Last updated on JULY 21, 2023

Applies to:

JDBC - Version 12.1.0.1.0 and later
Information in this document applies to any platform.

Symptoms

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.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.