RE: Locking records in DB2

> From: Paul Morgan
> 
> You're assuming the entire record gets updated but that might not be
the
> case.  For example I might have a customer file with billing and ship
to
> addresses on one customer record.  Just because the billing address
got
> updated while the ship to address was being edited doesn't mean we
have to
> throw away the ship to update.  Having one counter for the entire
record
> wouldn't allow concurrent updates to different parts of the record.

I assume you didn't get to the post where I talk about multiple counters
for independent data groups.  You're right, one counter per record only
works if all the fields need to be updated simultaneously.  But multiple
counters are in fact a very nice way to segregate field groups.

Joe