From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | Peter Newman <pnewman(at)wanadoo(dot)nl> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #1514: Inheritance and Primary Keys |
Date: | 2005-03-07 04:22:22 |
Message-ID: | 20050307042222.GA23449@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Mar 02, 2005 at 03:23:27PM +0000, Peter Newman wrote:
> So my point is (if it is not clear) that the primary key constraint is not
> enforced through subclass tables. Is this intentional?
It's a documented limitation of the current implementation. Here's
an excerpt from the "Inheritance" section of the "Data Definition"
chapter of the documentation:
A limitation of the inheritance feature is that indexes (including
unique constraints) and foreign key constraints only apply to
single tables, not to their inheritance children.
http://www.postgresql.org/docs/8.0/interactive/ddl-inherit.html
Fixing inheritance limitations is on the developers' TODO list --
it's just a matter of somebody deciding it's important enough to
work on.
http://developer.postgresql.org/todo.php
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
From | Date | Subject | |
---|---|---|---|
Next Message | Hans-Jürgen Schönig | 2005-03-07 10:44:59 | Re: BUG #1519: server closed the connection unexpectedly |
Previous Message | Peter Wright | 2005-03-06 22:47:13 | BUG #1528: Rows returned that should be excluded by WHERE clause |