"Rod Taylor" <rbt@zort.ca> writes:
> Did that originally with a function called MergeDomainAttributes()
> (since removed). The goal was to allow the user to change table
> attributes without overriding the domain. The constraints are
> 'merged' on execution for every other constraint type (default is
> wacky though), so don't see why NOT NULL should be special.
It appeared to me that the intention was to merge at table creation
time, not at execution. I would certainly recommend doing it that
way for simplicity and performance reasons. (This does put ALTER DOMAIN
out of reach, but I feel no pain at not supporting that.)
regards, tom lane
