From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Monday, October 28, 2013 12:15 PM
To: Midrange Systems Technical Discussion
Subject: 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 thenupdating
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
of until this morning) seems to only work for UPDATE and DELETE
statements, not SELECT.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact