| 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 be inherited |
| Date: | 2008-03-20 12:41:17 |
| Message-ID: | 20080320124117.GB6235@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | NikhilS | 2008-03-20 13:25:43 | Re: Problem identifying constraints which should not be inherited |
| Previous Message | Rui Martins | 2008-03-20 11:57:14 | Re: BUG #4044: Incorrect RegExp substring Output |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2008-03-20 13:16:04 | Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3 |
| Previous Message | Alvaro Herrera | 2008-03-20 12:36:51 | Re: Text <-> C string |