Tom Lane writes:
> Well, we *do* have a syntax for specifying a new default (the same one
> that worked pre-7.0 and does now again). I guess what you are proposing
> is the rule "If conflicting default values are inherited from multiple
> parents that each define the same column name, then an error is reported
> unless the child table redeclares the column and specifies a new default
> to override the inherited ones".
This was the idea. If it's to complicated to do now, let's at least keep
it in mind.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/