| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: Changing the default value of an inherited column |
| Date: | 2001-04-01 01:21:59 |
| Message-ID: | 3.0.5.32.20010401112159.0296d9c0@mail.rhyme.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 20:02 31/03/01 -0500, Tom Lane wrote:
>
>Perhaps we should just hack that code
>to not suppress inherited attrs when they have default values and/or
>NOT NULL that's not in the parent.
That's what I meant; can we easily do the 'not in the parent' part, since
we may have to go up a long hierarchy to find the parent?
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-04-01 01:25:44 | Re: Re: Changing the default value of an inherited column |
| Previous Message | Tom Lane | 2001-04-01 01:02:25 | Re: Re: Changing the default value of an inherited column |