Vlad Horsun wrote:

> User, even very experienced, can't prognose such things as number of
>fetches (or page reads). Statement execution time however is usually
>known to him. At least he can say for sure about upper time limit after
>which statement execution must be stopped. Per statement timeouts can
>be very useful for dynamic statements generated by application at run-time
>(especially if application has end-user constructor) and at time of development.
>
>IMO of course
>
>Regards,
>Vlad
>
>

Hi Vlad,

I agree with you that the number of fetches are a etereal measure for we
(me) simple mortals. But as mentioned to track the execution time will
be hard. I don't know about how difficult it is.

But one can say for example that an upper limit of 50000 (just a sample)
page fetches could be the upper limit.

My second question, now I know what fetches are, is:

1.) The partial result set will be returned to the user ?
2.) If the answer for the question 1 = true then a flag wll be returned
indicating that this is a partial result set ?
3.) If the answer for the question 2 = true the user could ask to
process N more fetches ?

Or the user will get just a time-out error ?

Sorry for the lame questions people, I just want to understand it a bit
more.

see you !

--

Alexandre Benson Smith
Development
THOR Software e Comercial Ltda.
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br



--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.6.9 - Release Date: 11/06/2005