From: Michael Glaesemann <grzm@seespotcode.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: George Pavlov <gpavlov@mynewplace.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: null values in non-nullable column
Date: Tue, 5 Dec 2006 13:05:22 +0900
Message-ID: <37EAE14E-EAC5-48E7-820B-B628C1B7BCF8@seespotcode.net> (raw)
In-Reply-To: <26730.1165290547@sss.pgh.pa.us>
References: <8C5B026B51B6854CBE88121DBF097A8661E3FC@ehost010-33.exch010.intermedia.net>
<25943.1165287166@sss.pgh.pa.us>
<A4835168-385E-4687-81CE-3AB29D260DFF@seespotcode.net>
<26730.1165290547@sss.pgh.pa.us>
On Dec 5, 2006, at 12:49 , Tom Lane wrote:
> Actually I think this is a bug in the SQL spec :-( The description of
> <joined table> says that output columns are "possibly nullable" if
> they're on the nullable side of the outer join, but it's not apparent
> that that idea is meant to negate a domain constraint. And yet, if it
> does not, then an outer join with a NOT NULL domain column on the
> nullable side is just invalid.
Very interesting. Thanks for the explanation. I should dig into the
spec more.
Michael Glaesemann
grzm seespotcode net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: grzm@seespotcode.net, tgl@sss.pgh.pa.us, gpavlov@mynewplace.com
Subject: Re: null values in non-nullable column
In-Reply-To: <37EAE14E-EAC5-48E7-820B-B628C1B7BCF8@seespotcode.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox