> > Someone can > > make it more efficient in regards to constraint checks, etc. in the > > future if they want -- I don't intend to. > > It'd be nice if you at least ensure that all the constraints are checked > in a single pass over the table (not one per constraint). Right offhand > I do not see why they couldn't be checked in the same pass that does the > UPDATE. For extra credit, detect that the default expression is > immutable or stable, and do the checks *once* not once per row.
I suppose that can be done. It will take a significant reorganization of the ALTER TABLE functions (or lots of duplicated code), but shouldn't be that time consuming. Anyway, I suppose you have indirectly confirmed that user triggers, etc. should NOT fire on for the data update. I didn't see anything in the spec that said one way or the other. -- Rod Taylor <[EMAIL PROTECTED]> PGP Key: http://www.rbt.ca/rbtpub.asc
signature.asc
Description: This is a digitally signed message part
