| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Precedence of standard comparison operators |
| Date: | 2015-03-12 11:16:55 |
| Message-ID: | CAM-w4HNDG_DBkXsk4GPsVOd6+X1gmYjx8JZgBOo0EDBKPMRGzg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 11, 2015 at 8:36 PM, Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
> Right; and they may have millions of lines of code which have been
> carefully tested and in production for years, and which may
> suddenly start to generate incorrect results on queries *or mangle
> existing data* with the fix unless they change their SQL code.
>
Well not suddenly. When doing a major upgrade. And we provide a tool to
help them identify the problems.
But having a warning enabled by default means the problem is effectively
not fixed at all. People will not be able to write code that's valid
according to the docs and the spec without extra parentheses or disabling
the warning.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2015-03-12 12:12:23 | Re: [PATCH] Add transforms feature |
| Previous Message | Jeevan Chalke | 2015-03-12 11:06:29 | Re: How about to have relnamespace and relrole? |