The Oracle issue related, but not caused by the same changes in the recent history of jOOQ 3.8 releases. It was caused by this new feature that was introduced in 3.8.0: https://github.com/jOOQ/jOOQ/issues/5190
I have implemented a fix on jOOQ 3.9 and will merge it today to 3.8.4: https://github.com/jOOQ/jOOQ/issues/5416 The solution is to fetch the SQL%ROWCOUNT value directly from PL/SQL, and not rely on JDBC's CallableStatement.executeUpdate() result, which is always 1 as there are always OUT parameters. Thanks again for reporting! Lukas 2016-07-14 16:30 GMT+02:00 Lukas Eder <[email protected]>: > Hmm, unfortunately, the Oracle issue is not strictly related to this most > recent regression in PostgreSQL, it was there before. I'll continue > investigating... > > 2016-07-12 12:21 GMT+02:00 <[email protected]>: > >> I encounter the same issue in Version 3.8.3 with Oracle 12C using >> record.update(). >> >> The query exposes SQL statement which starts with "begin update ... >> returning "MY_SCHEMA"."MY_TABLE"."MY_KEY" into ?; end;" >> If I prevent using >> org.jooq.impl.TableRecordImpl#setReturningIfNeeded >> in class >> org.jooq.impl.UpdatableRecordImpl#storeUpdate0 >> then the execute statement returns 0 on concurrent modification. >> >> For me this issue renders using record.update() useless. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "jOOQ User Group" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
