| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | 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-16 07:53:55 |
| Message-ID: | alpine.DEB.2.21.1807160950140.3767@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Heikki,
> The use case for transform_null_equals='warn' that I see is to wean off an
> application that uses transform_null_equals='on', to find all the queries
> that rely on it. But I'm not too excited about that either. The documented
> case for using transform_null_equals='on' is compatibility with Microsoft
> Access, and this wouldn't help with that. Besides, it's easy enough to grep
> the application or the server log for " = NULL", to find all such queries.
I'm in favor in having this feature, even if off by default, because I
could enable it and it would help my students when learning SQL in
interactive sessions, where "grep '= *NULL'" cannot be issued.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phil Florent | 2018-07-16 08:03:51 | RE: Internal error XX000 with enable_partition_pruning=on, pg 11 beta1 on Debian |
| Previous Message | Fabien COELHO | 2018-07-16 07:49:14 | Re: Make foo=null a warning by default. |