Re: Theoretical Basis for SELECT FOR UPDATE
- From: "x" <x@xxxxxxxxxxxxxx>
- Date: Fri, 30 Sep 2005 14:55:22 +0300
"Tony Andrews" <andrewst@xxxxxxxxxx> wrote in message
news:1128080541.493388.182640@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Marshall Spight wrote:
> I would say that SELECT FOR UPDATE is a valid facility in a DBMS that
> supports multi-statement transactions, even when cursors are not being
> used. It provides a means of locking data that was selected earlier in
> the transaction so that subsequent operations can use the selected data
> without risking violation of ACID properties (e.g. because another user
> deleted that row).
Locking is not part of the logical model. It has no place in a SELECT
statement.
.
- Follow-Ups:
- Re: Theoretical Basis for SELECT FOR UPDATE
- From: Tony Andrews
- Re: Theoretical Basis for SELECT FOR UPDATE
- References:
- Theoretical Basis for SELECT FOR UPDATE
- From: Marshall Spight
- Re: Theoretical Basis for SELECT FOR UPDATE
- From: Tony Andrews
- Theoretical Basis for SELECT FOR UPDATE
- Prev by Date: Re: Theoretical Basis for SELECT FOR UPDATE
- Next by Date: Re: Database design, Keys and some other things
- Previous by thread: Re: Theoretical Basis for SELECT FOR UPDATE
- Next by thread: Re: Theoretical Basis for SELECT FOR UPDATE
- Index(es):