Re: Another angle on this....

From what I've seen the behaviour is more extreme than implied by the other respondant.

Just because something has been committed it does not follow that even a select statement that begins *after* the commit will see it. As I understand it the guarantee from a select statement is that you will see a consistent view of the database, but not necessarily the most up-to-date. You can see this by doing an update then commit in one PLSQL session, and immediately querying the data on another connection. You don't always see the update that you just commited yet.

Slightly counter-intuitive, but having read the docs I think I can see the justification for this behaviour, on performance grounds.

Regards

Galen Boyer <galenboyer_at_hotpop.com> wrote in message news:<usn7jihpt.fsf_at_rcn.com>...
> On Thu, 21 Feb 2002, no.spam_at_ntlworld.com wrote:
>
> > The "don't necessarilly see recent commited updates from other users"
> > thing explains more fully
>
> Can you point me to where this was written about? I was under the
> impression that once data was committed it was able to be seen by all.
> I'd like to be aware of when this isn't the case.
Received on Sun Mar 03 2002 - 13:38:56 CST