Skip site navigation (1) Skip section navigation (2)

Re: Minor inheritance/check bug: Inconsistent behavior

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Chris Travers <chris(at)metatrontech(dot)com>, Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Minor inheritance/check bug: Inconsistent behavior
Date: 2012-08-27 20:11:56
Message-ID: CA+TgmoZg1SXqtFmGQ8qH_kiWVF5AOuM6GxdTpA=GuUYaBm0LEA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Fri, Aug 24, 2012 at 10:38 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Chris Travers <chris(at)metatrontech(dot)com> writes:
>> Table inheritance would be easier if there was a way to declare a
>> constraint such that it prevents insert for some rows on the parent
>> but not for a child and/or vice versa.
>
> FWIW, 9.2 adds support for constraints that only apply to the named
> table and don't get inherited to children.  I think use of such
> constraints is probably better design than mucking around with tableoid,
> even if we were to make that work.

Maybe, but in that case shouldn't referencing a system column chuck an error?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2012-08-27 20:34:01
Subject: Re: Minor inheritance/check bug: Inconsistent behavior
Previous:From: Tom LaneDate: 2012-08-27 19:31:08
Subject: Re: BUG #7507: pg_restore silently fails when restoring a db with the --create flag and no user.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group