Subject | Re: [ib-support] new & old context in CHECK constraints |
---|---|
Author | Martijn Tonies |
Post date | 2002-11-13T21:47:45Z |
Hi,
I expect this to work (or actually, I didn't - but hey) because a CHECK
constraints gets transformed (internally) in a set of two triggers, a BEFORE
UPDATE and BEFORE INSERT trigger. And if you look at it that way, the NEW.
thing and OLD. thing make sense again.
With regards,
Martijn Tonies
InterBase Workbench - the developer tool for InterBase
http://www.upscene.com
Firebird Workbench - the developer tool for Firebird
http://www.upscene.com
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."
ensure the user doesn't back up the date.
I expect this to work (or actually, I didn't - but hey) because a CHECK
constraints gets transformed (internally) in a set of two triggers, a BEFORE
UPDATE and BEFORE INSERT trigger. And if you look at it that way, the NEW.
thing and OLD. thing make sense again.
With regards,
Martijn Tonies
InterBase Workbench - the developer tool for InterBase
http://www.upscene.com
Firebird Workbench - the developer tool for Firebird
http://www.upscene.com
Upscene Productions
http://www.upscene.com
"This is an object-oriented system.
If we change anything, the users object."
> I'm not an expert, but I can tell you that I use this as well. I haveseveral dates that need to be incremented. I have a similiar check to
ensure the user doesn't back up the date.
>