| From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] BUG #2873: Function that returns an empty set |
| Date: | 2007-01-09 16:27:20 |
| Message-ID: | 25886.65.211.31.251.1168360040.squirrel@www.dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Tom Lane wrote:
> This is closely related to the discussion a couple weeks ago about how
> a LEFT JOIN could produce nulls in an output column that was labeled as
> having a non-null-domain type. We haven't figured out what is a sane
> behavior for that case, either. I'm beginning to think that domains
> constrained not null are just fundamentally a bad idea.
>
I think we just expect left joins to produce nulls regardless of
constraints on the underlying cols, don't we? Concluding that not null in
domains is bad seems a bit drastic.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-01-09 18:08:55 | Re: BUG #2875: pgAdmin III docs installed even if app is not |
| Previous Message | Tom Lane | 2007-01-09 14:56:23 | Re: [HACKERS] BUG #2873: Function that returns an empty set with a 'not null' domain errors in 8.2 but not 8.1 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew T. O'Connor | 2007-01-09 16:31:59 | Re: Autovacuum Improvements |
| Previous Message | Tom Lane | 2007-01-09 14:56:23 | Re: [HACKERS] BUG #2873: Function that returns an empty set with a 'not null' domain errors in 8.2 but not 8.1 |