Subject | Re: [firebird-support] Re: Checking periods don't overlap |
---|---|
Author | Jerome Bouvattier |
Post date | 2004-06-14T20:30:50Z |
John,
<quote>
select form checks should run in system context (my opinion, like
everything else I write). They were implemented during the years I was
away from the project and their developer may have decided differently.
Or may not have thought about the problem. If it were up to me, I'd fix
that in future versions. Such a change should have no effect on
running programs or existing databases and will avoid a small chance of
inconsistency creeping into the database and breaking the gbak restore.
Regards,
Ann
</quote>
I think I'd like triggers to be able to dirty-read too cause CHECKs
constraints won't fire in case of deletions.
Regards.
--
Jerome
> PS. Now I've learned that CHECK constraints can contain select's, IFYI, here's what Ann told me in an old thread :
> only want CHECK's to be able to dirty-read! Forget triggers.
<quote>
>I've played with some select-form CHECKs, and it seems they run in theSorry, I may have been generalizing without enough information. The
>*current* tx context unlike other constraints.
>
select form checks should run in system context (my opinion, like
everything else I write). They were implemented during the years I was
away from the project and their developer may have decided differently.
Or may not have thought about the problem. If it were up to me, I'd fix
that in future versions. Such a change should have no effect on
running programs or existing databases and will avoid a small chance of
inconsistency creeping into the database and breaking the gbak restore.
Regards,
Ann
</quote>
I think I'd like triggers to be able to dirty-read too cause CHECKs
constraints won't fire in case of deletions.
Regards.
--
Jerome