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

Re: Problem identifying constraints which should not beinherited

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: NikhilS <nikkhils(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Chris Fischer <Chris(dot)Fischer(at)channeladvisor(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Problem identifying constraints which should not beinherited
Date: 2008-03-20 12:41:17
Message-ID: 20080320124117.GB6235@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
NikhilS escribió:

> On Wed, Mar 19, 2008 at 8:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> > If it's a small patch, it's wrong by definition.  AFAICS there is no way
> > to fix this correctly that doesn't involve catalog changes.  The point
> > of the TODO is that you have to enforce that the inherited constraint
> > sticks around, eg can't be dropped on a child table while it's still
> > present on the parent.  There are implications for pg_dump too.
> 
> Ok, I understand. But even then this could patch could be considered even if
> it does not solve the TODO completely, no? It atleast disallows ONLY ADD
> CONSTRAINT on the parent.

No, because you would then feel that the TODO item is completed and not
provide a patch for the whole problem :-)

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

pgsql-hackers by date

Next:From: Martijn van OosterhoutDate: 2008-03-20 13:16:04
Subject: Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3
Previous:From: Alvaro HerreraDate: 2008-03-20 12:36:51
Subject: Re: Text <-> C string

pgsql-bugs by date

Next:From: NikhilSDate: 2008-03-20 13:25:43
Subject: Re: Problem identifying constraints which should not be inherited
Previous:From: Rui MartinsDate: 2008-03-20 11:57:14
Subject: Re: BUG #4044: Incorrect RegExp substring Output

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