pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Stephan Szabo <sszabo@megazone23.bigpanda.com>
Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Subject: Re: [GENERAL] child table doesn't inherit PRIMARY KEY?
Date: Wed, 24 Jan 2001 14:31:29 -0500 (EST)
Message-ID: <200101241931.OAA26463@candle.pha.pa.us> (raw)
In-Reply-To: <Pine.BSF.4.21.0101241120310.57849-100000@megazone23.bigpanda.com>

> On Wed, 24 Jan 2001, Bruce Momjian wrote:
> 
> > 
> > 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.
> 
> The problem is that doing that will pretty much guarantee that we won't
> be doing foreign keys to inheritance trees without changing that behavior
> and we've seen people asking about adding that too.  I think that this
> falls into the general category of "Make inheritance make sense" (Now 
> there's a todo item :) )  Seriously, I think the work on how inheritance
> is going to work will decide this, maybe we end up with a real inheritance
> tree system and something that works like the current stuff in which case
> I'd say it's probably one unique for the former and one per for the
> latter.

I smell TODO item.  In fact, I now see a TODO item:

* Unique index on base column not honored on inserts from inherited table
  INSERT INTO inherit_table (unique_index_col) VALUES (dup) should fail
  [inherit]

So it seems the fact the UNIQUE doesn't apply to the new table is just a
manifestion of the fact that people expect UNIQUE to span the entire
inheritance tree.  I will add the emails to [inherit] and mark it as
resolved.

-- 
  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



view thread (10+ messages)

Message-ID: <200101241931.OAA26463@candle.pha.pa.us>
Permalink:  ../200101241931.OAA26463@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200101241931.OAA26463@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: pgman@candle.pha.pa.us, sszabo@megazone23.bigpanda.com, pgsql-hackers@postgreSQL.org
  Subject: Re: [GENERAL] child table doesn't inherit PRIMARY KEY?
  In-Reply-To: <200101241931.OAA26463@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox