
I've got a table that has a primary key with a default of
nextval('seq').  I've got another table which inherits this one, but
it fails to inherit the unique btree index.  It does inherit the
default value.  So, I'm assuming that if I create a unique index for
that field on the child table, it won't keep you from inserting values
that exist in that field in the parent table (and since they both
share the same sequence, that's what I want).

So primary keys do not work in this situation.  Are there plans to
enhance the inheritance?  I have no idea how it works, is it
intelligent?  Seems more klunky than not, but I haven't really looked
at the code.  Should I stop using inheritance altogether, considering
its drawbacks (no idea what child class it is in when selecting from
parent and all children, no shared indices/pkeys) when I don't select
from them all at once?

Thu,  2 Apr 1998 21:42:53 -0800 (PST)
Brett McCormick <brett@work.chicken.org>
inherited sequences and primary keys 