Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: tough choices

Re: tough choices

From: Howard J. Rogers <hjr_at_dizwell.com>
Date: Sat, 19 Jun 2004 10:10:38 +1000
Message-ID: <40d38469$0$18666$afc38c87@news.optusnet.com.au>

"Daniel Morgan" <damorgan_at_x.washington.edu> wrote in message news:1087602573.649098_at_yasure...
> Howard J. Rogers wrote:
>
> > Some people talk about selects as though they were transactions. I
don't.
> > And those people would be wrong, IMO.
>
> I agree with one caveat:
>
> SELECT ...
> FROM ...
> FOR UPDATE;
>
> Which is the beginning of a transaction that must end with a commit or
> rollback.

Which is precisely why I included the sentence: "Selects don't (ordinarily) take locks in Oracle" in my original reply. The "ordinarily" was significant.

You may call it word games, but I wouldn't in any case regard a 'select for update' as being the same as a 'select', any more than I would regard an insert as being the same as an update. I very carefully said *selects* were not transactions.

Regards
HJR Received on Fri Jun 18 2004 - 19:10:38 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US