--- In firebird-support@yahoogroups.com, "Ivan Prenosil"
<Ivan.Prenosil@s...> wrote:

> > (relying on other records not inserted by
> > current transaction)

> There IS warning in documentation (not in red though):
> ----------
> Defining a CHECK constraint:
> Note: A CHECK constraint guarantees data integrity only when the

values being verified

> are in the same row that is being inserted and deleted. If you try

to compare values in

> different rows of the same table or in different tables, another

user could later modify

> those values, thus invalidating the original CHECK constraint that

was applied at insertion

> time.
> ----------

Thats not quite the whole story though is it? "..Other users could
later modify those values...". Well, actually they could have
*already* modified those values! And if you're in Snapshot, they
could have already committed those changes.

I'm impressed with your persistence in defending this blatantly
broken behaviour!

John