Tom Lane wrote:
Matthew Nourse <matt...@nplus1.com.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!
Matt
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
