From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200101241344.IAA12094@candle.pha.pa.us>
Subject: Re: [GENERAL] child table doesn't inherit PRIMARY KEY?
In-Reply-To: <Pine.BSF.4.21.0101190932480.5520-100000@megazone23.bigpanda.com>
	"from Stephan Szabo at Jan 19, 2001 09:37:02 am"
To: Stephan Szabo <sszabo@megazone23.bigpanda.com>
Date: Wed, 24 Jan 2001 08:44:16 -0500 (EST)
CC: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII


OK, what do people want to do with this item?  Add to TODO list?

Seems making a separat unique constraint would be easy to do and be of
value to most users.


> 
> Probably, since I see it in near recent sources (and it affects
> UNIQUE as well.  As I remember it, the last discussion on this couldn't
> determine what the correct behavior for unique/primary key constraints
> was in the inheritance case (is it a single unique hierarchy through
> all the tables [would be needed for fk to inheritance trees] or
> separate unique constraints for each table [which would be similar
> to how many people seem to currently use postgres inheritance as a 
> shortcut]). 
> 
> On Thu, 18 Jan 2001, Bruce Momjian wrote:
> 
> > Does this bug still exist?
> > 
> > [ Charset ISO-8859-1 unsupported, converting... ]
> > > Louis-David Mitterrand writes:
> > > 
> > > > When creating a child (through CREATE TABLE ... INHERIT (parent)) it
> > > > seems the child gets all of the parent's contraints _except_ its PRIMARY
> > > > KEY. Is this normal?
> 
> 


-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026