From: | NikhilS <nikkhils(at)gmail(dot)com> |
---|---|
To: | "Alvaro Herrera" <alvherre(at)commandprompt(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 be inherited |
Date: | 2008-03-20 13:25:43 |
Message-ID: | d3c4af540803200625s6904e31fw4275aa73770cb417@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Hi,
On Thu, Mar 20, 2008 at 6:11 PM, Alvaro Herrera <alvherre(at)commandprompt(dot)com>
wrote:
> 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 :-)
>
:)
Guess, I should have been wordier in my earlier response and should have
mentioned:
"This patch, if acceptable can be considered as a small step towards the
TODO"
too.
Regards,
Nikhils
--
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-03-20 14:01:53 | Re: BUG #4044: Incorrect RegExp substring Output |
Previous Message | Alvaro Herrera | 2008-03-20 12:41:17 | Re: Problem identifying constraints which should not be inherited |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-03-20 14:06:06 | Re: Problem identifying constraints which should not be inherited |
Previous Message | Martijn van Oosterhout | 2008-03-20 13:16:04 | Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3 |