Takahiro Itagaki wrote:
>
> Bruce Momjian <bruce@momjian.us> wrote:
>
> > Summary: ALTER TABLE SET NOT NULL on a parent table is passed to the
> > child, while ALTER TABLE ADD PRIMARY KEY is not, particularly the NOT
> > NULL part of the PRIMARY KEY specification.
> >
> > That does seem like something that should be fixed.
>
> Yeah, the issue is in our TODO list:
> http://wiki.postgresql.org/wiki/Todo
> | Move NOT NULL constraint information to pg_constraint
> | Currently NOT NULL constraints are stored in pg_attribute without
> | any designation of their origins, e.g. primary keys. One manifest
> | problem is that dropping a PRIMARY KEY constraint does not remove
> | the NOT NULL constraint designation. Another issue is that we should
> | probably force NOT NULL to be propagated from parent tables to children,
> | just as CHECK constraints are. (But then does dropping PRIMARY KEY
> | affect children?)
>
> And the same bug report has been here:
> http://archives.postgresql.org/message-id/200909181005.n8IA5Ris061239@wwwmaster.postgresql.org
> | BUG #5064: not-null constraints is not inherited
Ah, I see it on the TODO list now. Thanks.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
