> Do you plan to make Derby client behave this way too? Currently Derby
> client seems to match Embedded behavior if FOR UPDATE clause is not
> specified and statement is ResultSet.CONCUR_UPDATABLE... With Derby
> client, the cursor is *not *updatable in this case.
>
> Satheesh
Hi,
There is no need to make any changes to the Derby client to get this
feature also from the derby client driver. Its behaviour will continue
to match the Embedded behaviour on this feature.
After this change, the cursor will be updatable also from the Derby
client. So if the concurrency mode is CONCUR_UPDATABLE, you do not have
to specify "FOR UPDATE".
-- Andreas
