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.20010403115745.00c54de0@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>)
Responses Re: Re: Changing the default value of an inherited column  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At 13:27 2/04/01 -0400, Tom Lane wrote:
>
>Philip: the rule that pg_dump needs to apply w.r.t. defaults for
>inherited fields is that if an inherited field has a default and
>either (a) no parent table supplies a default, or (b) any parent
>table supplies a default different from the child's, then pg_dump
>had better emit the child field explicitly.
>

What is happening with IS NULL constraints (and type names)? I presume the
above rule should be applied to each of these fields?


----------------------------------------------------------------
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: Tom Lane
Date:
Subject: Re: Re: Changing the default value of an inherited column
Next
From: Tom Lane
Date:
Subject: Re: Re: Changing the default value of an inherited column