| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Make foo=null a warning by default. |
| Date: | 2018-07-16 01:40:42 |
| Message-ID: | 20180716014042.GS22932@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| 0001-Make-foo-null-a-warning-by-default.patch | text/x-diff | 11.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-07-16 02:10:36 | Refactor documentation for wait events (Was: pgsql: Add wait event for fsync of WAL segments) |
| Previous Message | Robert Haas | 2018-07-16 01:12:30 | Re: why partition pruning doesn't work? |