| From: | David Johnston <polobo(at)yahoo(dot)com> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: NULLs and composite types |
| Date: | 2013-12-12 19:25:31 |
| Message-ID: | 1386876331115-5783187.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Dean Gibson (DB Administrator)-2 wrote
> What's going on? I can provide more detail if requested. Of course, an
> obvious workaround is to use in a VIEW:
>
> ... NULLIF( location, ROW( NULL, NULL )::"GeoPosition" ) ...
>
> but I'd like to know the cause.
Cannot test right now but the core issue is that IS NULL on a record type
evaluates both the scalar whole and the sub-components. Try using IS [NOT]
DISTINCT FROM with various target expressions and see if you can get
something more sane.
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/NULLs-and-composite-types-tp5783027p5783187.html
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Gibson (DB Administrator) | 2013-12-12 21:57:42 | Re: NULLs and composite types |
| Previous Message | Vick Khera | 2013-12-12 16:29:07 | Re: [GENERAL] Scheduled Events |