On Thursday 10 May 2001 10:06, Jacques Kilchoer wrote:
> This reminds me, Mr. Still, you posted an example once to the list about
> doing a fetch in rowid order to avoid revisiting the same block when doing
> a full table scan of a table, so that reading and updating every row in a
> table would avoid the dreaded "snapshot too old". I told a developper about
> that today and showed him a code sample, but he says he still had a
> "snapshot too old". Would it be possible for you to post that snippet of
> code again?
>
> Jacques R. Kilcho�r
> x8816
Wow, that sounds pretty cool.
You say I did that? :)
I'll take a look, but I'm not sure if I still have that. This sounds
familiar, but I can't remember it at the moment.
In the meantime, take a couple of hours and walk through the
developers code. My experience is that they either can't or
won't do a 'desk check' and don't really know what is going
on in their own code.
They also often commit too frequently or not often enough, or
do a commit while a update cursor is open and wonder why
they get a fetch across commit error on the next fetch.
Jared
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Jared Still
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
