Re: Re: Changing the default value of an inherited column - Mailing list pgsql-hackers

From Philip Warner
Subject Re: Re: Changing the default value of an inherited column
Date
Msg-id 3.0.5.32.20010401120936.00ae0b20@mail.rhyme.com.au
Whole thread Raw
In response to Re: Re: Changing the default value of an inherited column  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At 21:00 31/03/01 -0500, Tom Lane wrote:
>
>If we change the code again based on the latest discussion, then pg_dump
>would have to detect whether there are conflicting defaults, which would
>mean looking at all the parents not just the rightmost one.  Ugh.  That
>might be a good reason not to change...
>

Shall I hold off on this for a day or two to let the other discussion
settle down? It seems whatever happens, we should check NOT NULL.


----------------------------------------------------------------
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   |/


pgsql-hackers by date:

Previous
From: "Johnny Cristensen"
Date:
Subject: Complete Database Permission
Next
From: Roberto Mello
Date:
Subject: [pgsql-hackers-owner+M6959@postgresql.org: Majordomo Delivery Error]