Thread: row level locking?

I have an update statement (no transaction controls surround these
statements):

update sessions set sessdate = 0 where sessid in ( long list of ids);

How long will the rows being updated be locked for this statement? Will all
be locked until all updates are completed or will the row locking only occur
for each row being updated?

If I have a statement like:

update sessions set sessdate = 0 where datetime < 10000; (this would be the
same criteria that created the list used above)

How long will each row be locked for?

These queries can be updating a good number of rows ( > 10,000) every 10
minutes and I need to figure out how signifigant of an impact the locking
occuring in those updates can be.

On Mon, 10 Sep 2001, Jeff Barrett wrote:

> I have an update statement (no transaction controls surround these
> statements):
> 
> update sessions set sessdate = 0 where sessid in ( long list of ids);
> 
> How long will the rows being updated be locked for this statement? Will all
> be locked until all updates are completed or will the row locking only occur
> for each row being updated?

AFAIK until the end of statement (since it's wrapped in an implicit
transaction)

> If I have a statement like:
> 
> update sessions set sessdate = 0 where datetime < 10000; (this would be the
> same criteria that created the list used above)

Should be the same I would guess.