On Monday 04 August 2003 11:19, Olivier Mascia wrote:

>
> Just run your statement inside a default Firebird transaction (which is
> of type "Concurrency" and you'll get consistent results for your
> max(foo), without seeing the other transactions commits, yet without
> blocking those other transactions to write and commit.
>

It ought to be remembered that almost all middleware driver type stuff thinks
that the default transaction isolation should be read committed. So, while
Firebird itself may default to concurrent isolation (best and cleanest imo)
the connectivity layer may have other ideas. It is best to check on a driver
by driver basis what each one defaults to.


Paul
--
Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird and InterBase