Sorry, I have been out for a while.
Just wanted to say that
Read committed is the default and was the only
automatic isolation level provided before Oracle
Release 7.3.
And Read committed is still the default which doesn't
let anybody even within the transaction see the
updated changes.
triggers work for example. There is a freaky
option in Oracle they
put in just to blow out the TPC-A benchmark,
discrete transactions, that
doesn't let you read changes during the transaction.
Cheers
Jay
-Original Message-
From: Gina Hagg [mailto:[EMAIL PROTECTED]]
Sent
and, this is from the same page as before.
http://technet.oracle.com/doc/server.815/a67781/c23cnsis.htm#2570
Oracle Isolation Levels
Oracle provides three transaction isolation levels:
read committed
This is the default transaction isolation level. Each
query executed by a transaction sees
Marc,
is the interactive survey done yet?
if it is not done, who is team lead?
i like to get involved, since i have a bit of time..
Gina
__
Do You Yahoo!?
Spot the hottest trends in music, movies, and more.
http://buzz.yahoo.com/
on Oracle 8.1.7.
Maybe older versions
work
differently.
Bill
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On
Behalf Of
Gina
Hagg
Sent: Friday, June 15, 2001 5:53 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] No storeEntity before
u that I really don't agree with, that database
guys can see the change
outside the commit within the same transaction seems
kind of funky to me...
but it is in the spec so...
I have been working with databases for a long time,
and particularly with Oracle, I am not aware that this
Just to confirm what Jay is saying...
I was recently at an Oracle workshop, and since the
rowid isn't part of the ANSI SQL standard and is a
proprietary pseudo column, they warned us again using
it in building applications. They said, the
improvements could be wiped out in a future release of
