Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
> That said, it is trivial to clean up the internal code as I propose but
> to *also* support the default backslash (not SQL9x compliant, but what
> the heck ;) by simply passing the right parameter to the new "two
> argument" like() support routines. That parameter could be set back to
> NULL after the next release to get us back to SQL9x compliance.
Sure. I'm merely arguing that the default behavior needs to be to treat
backslash as escape by default for at least one more release. You need
to give people warning and time to update their applications to say
"LIKE ... ESCAPE '\\'", if that's the behavior they want to have going
forward.
regards, tom lane
