Re: Oracle Select/Insert Locking

M2 wrote:

I think part of what is causing the problem in understanding why you even have a problem is the following:

"The problem is the race condition that is possible when parallel hits occur for the same user and the same message."

Could you please translate into English what you mean by a "RACE" condition? This is the first time I have ever seen this term and I think it is hiding your actual meaning.

If the same user can read the same message multiple times then you have a very bad design: It should be impossible. Look at SELECT FOR UPDATE. Also seriously look at the DBMS_AQ and DBMS_AQADM packages.

Thanks.

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)