> >>Elapsed time.
> >
> > Well, a direct compare doesn't suit our needs perfectly. A user who has

an

> > active grid with some not yet fetched rows will get a timeout error as

soon

> > as he press the "down" key. Perhaps it's better to track the time spent

in

> > the looper.
>
> Why not use the fetch count? Yes, I realize that the user doesn't know
> what a fetch is - nor does the user know what a trip through looper
> means. We already count fetches so there's no extra overhead. A bit of
> experimentation on our part could set up some guidelines - e.g. < 50000
> fetches is low, < 500000 fetches is moderate, < 5000000 fetches is high,
> other is unlimited.

Because it doesn't make sense... See my web-server example.

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com