Re: Theoretical Basis for SELECT FOR UPDATE

My question is this: what is the best way for putting toghether two
languages (the host language and the data sublanguage) without breaking the
ACID and maximizing concurrency.

A cursor try to imitate a sequential file of records.

"Marshall Spight" <marshall.spight@xxxxxxxxx> wrote in message
news:1128057843.378642.38150@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi all,
>
> I am interested to hear people's opinions on the validity
> of SELECT FOR UPDATE. It is not something that I've ever
> had to use, or even felt the need for, but I don't confuse
> that fact with any kind of proof or disproof of the technique's
> essentiality.
>
> Also, if I understand correctly, TTM doesn't like it at all,
> either. It appears "RM Proscription 7" forbids the technique.
> I give a fair bit of weight to TTM, but I don't necessarily
> agree with everything it says, nor do I believe that the
> solutions it proposes to problems are the only or even
> the best solutions. In this case, they simply disallow it,
> but don't provide any alternative, which suggests that they
> feel it is simply unnecessary.
>
> I am interested to hear people's experiences, and especially
> any insight into the "true nature" of cursors and/or select
> for update, and whether it is in fact necessary.
>
>
> Marshall
>


.