Make foo=null a warning by default. - Mailing list pgsql-hackers

From David Fetter
Subject Make foo=null a warning by default.
Date
Msg-id 20180716014042.GS22932@fetter.org
Whole thread Raw
Responses Re: Make foo=null a warning by default.  (Heikki Linnakangas <hlinnaka@iki.fi>)
Re: Make foo=null a warning by default.  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
Folks,

Per a discussion with Andrew Gierth and Vik Fearing, both of whom
helped make this happen, please find attached a patch which makes it
possible to get SQL standard behavior for "= NULL", which is an error.
It's been upgraded to a warning, and can still be downgraded to
silence (off) and MS-SQL-compatible behavior (on).

Best,
David.
-- 
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: why partition pruning doesn't work?
Next
From: Michael Paquier
Date:
Subject: Refactor documentation for wait events (Was: pgsql: Add wait eventfor fsync of WAL segments)