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

From Tom Lane
Subject Re: Re: Changing the default value of an inherited column
Date
Msg-id 26696.986270250@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: Changing the default value of an inherited column  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: Re: Changing the default value of an inherited column  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
Philip Warner <pjw@rhyme.com.au> writes:
> 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)?

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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Philip Warner
Date:
Subject: Re: Re: Changing the default value of an inherited column
Next
From: Tom Lane
Date:
Subject: Do we have any platforms that allow null pointer dereference?