| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Make foo=null a warning by default. |
| Date: | 2018-07-17 11:58:50 |
| Message-ID: | alpine.DEB.2.21.1807170744380.29486@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
> Yeah, I was wondering about that too. But Fabien brought up a completely new
> use-case for this: people learning SQL.
Indeed.
This year, about 30% of my students wrote "= NULL" in a query at least
once. Probably I or a colleague were called to the rescue for help.
So this warning would save me time, which explains why I reviewed the
patch with such enthousiasm:-)
I'm fine with keeping the current behavior as a default.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haribabu Kommi | 2018-07-17 12:15:12 | Re: Libpq support to connect to standby server as priority |
| Previous Message | Andrey Klychkov | 2018-07-17 11:48:36 | Re[2]: Alter index rename concurrently to |