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.20010403185536.00c34320@mail.rhyme.com.au
Whole thread Raw
List pgsql-hackers
At 23:57 2/04/01 -0400, Tom Lane wrote:
>
>NOT NULL on a child field would only force it to be dumped if none
>of the parents say NOT NULL.  Type name really is not an issue since
>it will have to be the same in all the tables anyway; I wouldn't bother
>expending any code there.
>

Done & applied to CVS. Only dumps changed info, so:
   create table p3_def1(f1 int default 1, f2 int);   create table c5(f1 int not null, f3 int) inherits(p3_def1);

will get dumped as:
   CREATE TABLE "c5" (       "f1" integer NOT NULL,       "f3" integer   )   inherits ("p3_def1");

ie. without the DEFAULT.


----------------------------------------------------------------
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: Philip Warner
Date:
Subject: Re: Re: Changing the default value of an inherited column
Next
From: Zeugswetter Andreas SB
Date:
Subject: Re: capitalized sql (was: Re: Changing the default valu e of an inherited column)