Paul Reeves wrote:

> 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.

I could not tell it better. :)
Yet, I'm still convinced the task Raj has at hands is simulating a
generator. So the very best solution would be to use a generator and not
simulate it with a MAX() which would (Raj is correct here) require
locking. Generator solution implies no table or row-locking at all.

--
Olivier Mascia