Thats a good idea, thanks Alan.

Like maybe a timestamp field, 'certified ok at...' kind of thing??
Or a generator (same values in all 'good' rows). Smaller than a
timestamp.

You'd still have to check everytime you opened a transaction though
(slooow) - or use an older 'certificate'.

John

PS. Now I've learned that CHECK constraints can contain select's, I
only want CHECK's to be able to dirty-read! Forget triggers.


--- In firebird-support@yahoogroups.com, "Alan McDonald" <alan@m...>
wrote:

> Do you do back/forward passes? you could alert the user there or

mark

> conficting records and leave them out of further calcs?
> Alan