Don't have a db in front of me at the moment (I'm at home) create small
table with a primary key. user one inserts a record with a primary key
value of 1 then user 2 inserts a record with primary key value 2. should
get the constraint violated at this point.
Jim
--
Replace part of the email address: kennedy-down_with_spammers_at_attbi.com
with family. Remove the negative part, keep the minus sign. You can figure
it out.
"Dusan Bolek" <pagesflames_at_usa.net> wrote in message
news:1e8276d6.0307290059.10fe3c37_at_posting.google.com...
> "Jim Kennedy" <kennedy-downwithspammersfamily_at_attbi.net> wrote in message
news:<qqCUa.154597$H17.54867_at_sccrnsc02>...
> > Dirty reads are not a feature they are a
> > failing. Oracle itself does do dirty reads; it just does not allow you
the
> > user to do them. (eg trying to insert a row with a repeated primary key
> > where the repeat was inserted in an uncommitted transaction that you
cannot
> > see. Error will be raised because the primary key violation. Case of
> > Oracle "looking behind the scenes - doing a dirty read".)
>
> Sorry, but do you have any proof for this or can you supply a version
> number/parameters/test case where Oracle behave like this?
> Maybe I'm missing something obvious, but other guy should be locked
> and get "constrain violated" message AFTER first guy will commit his
> transaction.
>
> --
> Dusan Bolek
Received on Tue Jul 29 2003 - 07:45:06 CDT
