
www.Usenet.com
| <-- __Chronological__ --> | <-- __Thread__ --> |
While stranded on information super highway mcstock wrote:
:)
:)"Daniel Morgan" <[EMAIL PROTECTED]> wrote in message
:)news:[EMAIL PROTECTED]
:)| D Alpern wrote:
:)|
:)| > SELECT... FOR UPDATE {WAIT | NOWAIT} springs to mind...
:)| >
:)| > David
:)|
:)| Why would that spring to mind?
:)|
:)| It doesn't block a read which is the point of the OP's request.
:)|
:)| --
:)| Daniel Morgan
:)| http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
:)| http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
:)| [EMAIL PROTECTED]
:)| (replace 'x' with a 'u' to reply)
:)|
:)
:)actually, it does... it voluntarily blocks the read that it itself
:)(grammar?) is attempting to do
:)
:)so, on a case by case basis (instead of a session or instance isolation
:)level setting), the reader gets blocked by the writer
:)
:)unfortunately, the reader that uses this syntax now blocks writers, but if
:)serialization is what's required to meet the business requirement, this
:)would seem to do it
:)--
:)Mark C. Stock
:)mcstock -> enquery(dot)com
:)www.enquery.com training & consulting
:)
This will not work.
I have to read the next row to find out what it is and then delete it.
If another process has already deleted the row, I should be getting the old
value. Oracle will not block readers.
:)
:)
--
Hemant Shah /"\ ASCII ribbon campaign
E-mail: [EMAIL PROTECTED] \ / ---------------------
X against HTML mail
TO REPLY, REMOVE NoJunkMail / \ and postings
FROM MY E-MAIL ADDRESS.
-----------------[DO NOT SEND UNSOLICITED BULK E-MAIL]------------------
I haven't lost my mind, Above opinions are mine only.
it's backed up on tape somewhere. Others can have their own.
| <-- __Chronological__ --> | <-- __Thread__ --> |