Re: Oracle Select/Insert Locking

From: Daniel Morgan <damorgan_at_x.washington.edu>
Date: Fri, 13 Feb 2004 14:31:59 -0800
Message-ID: <1076711473.483919@yasure>

Ed prochak wrote:

> Daniel Morgan <damorgan_at_x.washington.edu> wrote in message news:<1076533565.155270_at_yasure>...
>

>>Bricklen wrote:
>>
>>
>>>"A race condition is an undesirable situation that occurs when a device 
>>>or system attempts to perform two or more operations at the same time, 
>>>but because of the nature of the device or system, the operations must 
>>>be done in the proper sequence in order to be done correctly."
>>>
>>>http://searchstorage.techtarget.com/sDefinition/0,,sid5_gci871100,00.html
>>
>>Thanks. Still looks like nothing more than bad design.

>
>
> Daniel,
> I think the OP is working for one of those managers that likes his
> developers to violate the laws of physics on a regular basis.
>
> Bricklen,
> Why Daniel thinks this is bad design is partly because you never
> stated your business need. Your design might not answer the real need,
> another design may be better. If you really want that insert to work,
> you will have to create and use a monitor process (ie, force this to
> be a single threaded transaction). That would work but be a
> performance nightmare.
>
> hth,
> ed

You are correct. Also because I have never experienced the problem he describes in more than a decade of working with Oracle in VLDB environments with hundreds of thousands of users. Thus ... it seems to me to be the result of the design until demonstrated to be caused by something else.

-- 
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)

Received on Fri Feb 13 2004 - 16:31:59 CST