Wrong Update Behavior With Newly Fetched Data Incorrectly Using Updated Values From Existing Rows In The Query For Insensitive, Updatable Resultsets
Last updated on APRIL 05, 2017
Applies to:JDBC - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
When working with resultsets that are both updatable and insensitive, newly fetched data incorrectly uses updated values from existing rows in the query. This manifests at boundary rows of the fetch size (the default fetch size is 10).
If the fetch size is 10, then the existing value of 10th column and 11th column are the same, and the update operation is performed based on the existing value, then the problem occurs with the 11th row. This will repeat at each boundary (so if the fetch size is 10, the problem will also occur for the 20th/21st rows, the 30th/31st rows, and so on).
For example: Given a resultset created with the specifications ResultSet.TYPE_SCROLL_INSENSITIVE and ResultSet.CONCUR_UPDATABLE...
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms