diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2009-10-10 03:50:15 +0000 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2009-10-10 03:50:15 +0000 |
commit | 05d249717d652f0b16960d8a58611e222f1f907b (patch) | |
tree | f5999862b949fc1c991d3d7e2ff51ed170656de1 /src/backend/executor/execProcnode.c | |
parent | 8a5849b7ff24c637a1140c26fc171e45c9142005 (diff) | |
download | postgresql-05d249717d652f0b16960d8a58611e222f1f907b.tar.gz postgresql-05d249717d652f0b16960d8a58611e222f1f907b.zip |
Improve similar_escape() in two different ways:
* Stop escaping ? and {. As of SQL:2008, SIMILAR TO is defined to have
POSIX-compatible interpretation of ? as well as {m,n} and related constructs,
so we should allow these things through to our regex engine.
* Escape ^ and $. It appears that our regex engine will treat ^^ at the
beginning of the string the same as ^, and similarly for $$ at the end of
the string, which meant that SIMILAR TO was effectively ignoring ^ at the
start of the pattern and $ at the end. Since these are not supposed to be
metacharacters, this is a bug.
The second part of this is arguably a back-patchable bug fix, but I'm
hesitant to do that because it might break applications that are expecting
something like "col SIMILAR TO '^foo$'" to work like a POSIX pattern.
Seems safer to only change it at a major version boundary.
Per discussion of an example from Doug Gorley.
Diffstat (limited to 'src/backend/executor/execProcnode.c')
0 files changed, 0 insertions, 0 deletions