I'll have a look-see since it's in the vicinity of the code I'm messing with
at the moment. Time is my problem, though...
Chris
> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Tom Lane
> Sent: Wednesday, 9 May 2001 11:00 PM
> To: Philip Warner
> Cc: PostgreSQL-development
> Subject: Re: [HACKERS] Outstanding patches
>
>
> Philip Warner <pjw@rhyme.com.au> writes:
> > Is anybody planning to fix the problem with ALTER TABLE ADD
> CONSTRAINT...
> > in which the constraints are not applied to child tables?
>
> AFAIK no one is looking at it presently (although Stephan Szabo has
> probably thought about it). If you want to tackle it, step right up,
> but coordinate with Stephan.
>
> I was just in the vicinity of ALTER TABLE, and noted that that routine
> didn't have the same loop-over-children superstructure that most of the
> other ALTER code does. Should be a relatively simple matter to graft
> that logic onto it, unless there are semantic funnies that come up with
> propagating the new constraint.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
