Re: JDBC record locking -- help?

On 10/28/13 9:51 AM, Dan Kimmel wrote:

How about reading the table with a CONCUR_READ_ONLY and then updating
it with an UPDATE statement with a where clause rather than an UPDATE
CURRENT of your record set?

The difficulty with that is that I know of no way to do an UPDATE statement that does all the columns by result set column number (the way updateString() and so forth, followed by an updateRow(), does), and building a statement to update all the columns by name (when, at compile time, we don't even know how may columns we have, let alone what their names are) is even less convenient than briefly opening an updateable result set on the same query as an existing read-only result set.

And naturally, WHERE CURRENT OF <cursorName> (which I hadn't even heard of until this morning) seems to only work for UPDATE and DELETE statements, not SELECT.

--
JHHL