| From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "George Pavlov" <gpavlov(at)mynewplace(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: null values in non-nullable column |
| Date: | 2006-12-05 04:05:22 |
| Message-ID: | 37EAE14E-EAC5-48E7-820B-B628C1B7BCF8@seespotcode.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marian POPESCU | 2006-12-05 15:25:31 | transaction in function |
| Previous Message | Tom Lane | 2006-12-05 03:49:07 | Re: null values in non-nullable column |