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

Andreas Korneliussen wrote:

There is no "setting to read only" as part of this patch, it is rather the oposite.  Today, the updatemode always defaults to read only if the updateclause is unspecified. The change is simply to allow the cursor to be UPDATABLE if the concurrency mode for the statement is ResultSet.CONCUR_UPDATABLE.

-- Andreas

Reply via email to