> > Yeah, I have already hacked it a bit. This constraint now needs to be
> > spit out later as an ALTER command with ONLY attached to it
> > appropriately. Earlier all CHECK constraints were generally emitted as
> > part of the table definition itself.
> Hrm.  That doesn't seem so good.  Maybe we've got the design wrong
> here.  It doesn't seem like we want to lose the ability to define
> arbitrary constraints at table-creation time.
Well the handling is different now for "ONLY" constraints only. The normal
constraints can still be attached at table-creation time.


Reply via email to