Tom Lane wrote:
>I just had a discussion with a user who doesn't want to update from
>6.4.something to 7.0.* because 7.0 broke a feature he likes, namely
>the ability to change the default value of a column inherited from
>a parent table. It seems that in pre-7.0 Postgres, this works:
>create table one(id int default 1, descr text);
>create table two(id int default 2, tag text) inherits (one);
>with the net effect that table "two" has just one "id" column with
>default value 2.
>The question of the day: should we put this back the way it was?
>If so, should we try to squeeze it into 7.1, or wait another release
>cycle? (I can see about equally good arguments for considering this
>a feature addition or a bug fix...) Should there be a NOTICE about
>the duplicated column name, or is the old silent treatment okay?
I would very much like to have this feature restored; I think there should
be a NOTICE, just in case the duplication is caused by mistyping.
Oliver Elphick Oliver(dot)Elphick(at)lfix(dot)co(dot)uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47 6B 7E 39 CC 56 E4 C1 47
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
"Trust in the Lord with all your heart and lean not on
your own understanding; in all your ways acknowledge
him, and he will direct your paths." Proverbs 3:5,6
pgsql-hackers by date
|Next:||From: Oliver Elphick||Date: 2001-03-29 13:29:38|
|Subject: Re: Re: Changing the default value of an inherited column |
|Previous:||From: Jan Wieck||Date: 2001-03-29 12:12:34|
|Subject: Re: Re: [HACKERS] Re: [PORTS] pgmonitor and Solaris|