Re: [BUGS] BUG #14665: Wrong IS NULL result for composite type that has composite element - Mailing list pgsql-bugs

From Tom Lane
Subject Re: [BUGS] BUG #14665: Wrong IS NULL result for composite type that has composite element
Date
Msg-id 1258.1495551376@sss.pgh.pa.us
Whole thread Raw
In response to [BUGS] BUG #14665: Wrong IS NULL result for composite type that hascomposite element  (julius.tuskenis@gmail.com)
List pgsql-bugs
julius.tuskenis@gmail.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


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: julius.tuskenis@gmail.com
Date:
Subject: [BUGS] BUG #14665: Wrong IS NULL result for composite type that hascomposite element
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] BUG #14662: 'has_table_privilege()' function fails with error, "invalid name syntax" when using Japanese symbols