On Wed, Mar 11, 2015 at 8:36 PM, Kevin Grittner <kgri...@ymail.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
