From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hackers List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: LIKE pattern matching |
Date: | 2000-08-07 17:05:34 |
Message-ID: | 398EEC5E.6B7FD7D4@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > 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.
OK. I was worried that leaving in the explicit "escape code" in the
routines will lead to bad behavior wrt both old releases *and* SQL9x.
But providing the default argument while still cleaning up the internal
code probably does The Right Thing.
- Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2000-08-07 17:23:44 | Re: Constraint stuff |
Previous Message | Tom Lane | 2000-08-07 17:02:11 | Re: mac.c |