Nando Dessena wrote:

>
> ... Unfortunately,
> database-agnostic tools and libraries need to map Firebird's
> transaction settings to something...

Since Firebird, Postgres, and now (with Falcon) MySQL all have
a consistent read, perhaps tools should make an accommodation to
that level of consistency.

And I should have mentioned that the InnoDB storage engine
of MySQL doesn't have phantoms unless you use the FOR UPDATE
qualifier on select. Nor does Oracle. Consistent read is
neither delicate (compared to repeatable read with read/write
locks) nor rare.

Regards,


Ann