Re: BUG #14665: Wrong IS NULL result for composite type that has composite element

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: julius(dot)tuskenis(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14665: Wrong IS NULL result for composite type that has composite element
Date: 2017-05-23 14:56:16
Message-ID: 1258.1495551376@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

julius(dot)tuskenis(at)gmail(dot)com writes:
> The problem is with the composite types that have composite types in them.
> In cases then a subtype has all NULL fields the type is still evaluated NOT
> NULL.

Yeah, it's not recursive. We concluded that that's correct per the
text of the SQL standard. See discussion here:

https://www.postgresql.org/message-id/flat/20160708024746.1410.57282%40wrigleys.postgresql.org

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-05-23 15:20:47 Re: BUG #14662: 'has_table_privilege()' function fails with error, "invalid name syntax" when using Japanese symbols
Previous Message julius.tuskenis 2017-05-23 13:53:27 BUG #14665: Wrong IS NULL result for composite type that has composite element