"Alex Hunsaker" <[EMAIL PROTECTED]> writes:
> create table junk (val integer not null, val2 integer);
> create table junk_child () inherits (junk_1);
> alter table junk_child alter column val drop not null;
> insert into junk_child (val2) values (1);
> pg_dump -t junk -t junk_child
> pg_restore/psql will fail because junk_child.val now has a not null
> constraint
Actually the bug is that ALTER TABLE allows you to do that. It should
not be possible to drop an inherited constraint, but right now there's
not enough information in the system catalogs to detect the situation.
Fixing this has been on the TODO list for awhile:
o %Prevent child tables from altering or dropping constraints
like CHECK that were inherited from the parent table
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
