Tom Lane wrote:
> Matthew Nourse <matthew(at)nplus1(dot)com(dot)au> writes:
>> As NOT NULL on domains doesn't always prevent a value from becoming NULL
>> (and because it "sucks" :) ) would you consider deprecating the
>> not-null-on-domains feature and then removing it from some future
>> version of PostgreSQL?
> We can't really because it's required by SQL standard. Perhaps at some
> point the standards committee will think it through a little better and
> publish something that resolves the contradictions. For the moment the
> bottom line is that it's got debatable behavior and is best avoided.
Ah, I see. Thanks again!
In response to
pgsql-bugs by date
|Next:||From: Greg Stark||Date: 2010-05-31 01:58:48|
|Subject: Re: BUG #5459: Unable to cancel query while in send()|
|Previous:||From: Tom Lane||Date: 2010-05-30 17:54:14|
|Subject: Re: BUG #5477: CREATE DOMAIN NOT NULL constraints not always enforced for INSERT with subquery |