Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Which transaction isolation level can prevent lost updates?
"Daniel Morgan" <dmorgan_at_exesolutions.com> wrote in message
news:3DE2943C.B7201C05_at_exesolutions.com...
> Arno Huetter wrote:
>
> > Hello there,
> >
> > I am working on a multi-tier project, using Oracle 8i. My data layer
> > consists of container-managed entity java beans, which means that I
> > don't have direct control over which SQL statements are being
> > generated, hence I cannot force X-locks via dummy-updates, nor by
> > invoking SELECT FOR UPDATE.
<snip>
> In Oracle the chances of this problem happening is so remote that I can't
> think of anyone that does anything to code around it. Definitely not
> changing isolation levels.
>
> Are you sure you really have a problem that can't be solved with SELECT
> FOR UPDATE?
sure he does. the data layer code is frozen/unchangeable but nonscalable and
buggy so he is supposed to work around it. Who knows it might even be
'platform independent'.
cynically yours
-- Niall Litchfield Oracle DBA Audit Commission UK ***************************************** Please include version and platform and SQL where applicable It makes life easier and increases the likelihood of a good answer ******************************************Received on Mon Nov 25 2002 - 15:33:17 CST
![]() |
![]() |