Heyho! (Ok, seems to be feature wish day ...) I was wondering if others would find an IMMUTABLE (or whatever) column constraint useful as well. Semantics would (obviously?) be to disallow changing the value of this column after insert. I realize that this is possible via triggers, and with the recent possibility of having triggers fire only on changes to certain columns it's even (presumably) not much runtime overhead, but creating triggers is very verbose and doesn't make the db schema very readable. cheers -- vbi -- Could this mail be a fake? (Answer: No! - http://fortytwo.ch/gpg/intro)
Attachment:
signature.asc
Description: This is a digitally signed message part.
