> > Seems like a bad idea to
> > me. But as long as the default is to propagate these changes, I'm not
> > really eager to prohibit DBAs from doing the other. Who's to say what's
> > a misuse of inheritance and what's not...
>
> At the moment we have:
>
> * ADD CONSTRAINT does not propagate
> * If you create a table with a CHECK constraint, then create a table that
> inherits from that, the CHECK constraint _does_ propagate.
>
> Seems to me that these behaviours are inconsistent...
Yep, but I've got the minimal patch to fix ADD CONSTRAINT. I'm just
waiting for the upcoming weekend so I can add the regression tests and
pack it up.
