RE: Locking records in DB2

>If you're going to do this, please include the code that checks for
lack
>of update.  I assume there is some magic field in the SQL return data
>that indicates the number of records updated; if that value is zero,
>then perform the "record was updated by someone else" logic.

You want the "rows effected" value. How you get it depends on the
interface you're using for SQL. From RPG you'd look at the SQLER3 field
after the update. From .NET you'd inspect the return code from
ExecuteNonQuery(). From Java you'd look at the return code of the
executeUpdate().


>This is not a good reason, especially if you have encapsulated your
>updates in a single place.  

Or have properly used SQL for your reads and writes. SQL doesn't care
how many fields I add to the end of my table (or the middle, or the
beginning) it's going after named fields.

-Walden

------------
Walden H Leverich III
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)