From: | Zalman Stern <zalman(at)netcom(dot)com> |
---|---|
To: | maillist(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian) |
Cc: | zalman(at)netcom(dot)com, herouth(at)oumail(dot)openu(dot)ac(dot)il, pgsql-sql(at)postgreSQL(dot)org |
Subject: | Re: [SQL] How match percent sign in SELECT using LIKE? |
Date: | 1999-03-16 22:55:33 |
Message-ID: | 199903162255.OAA28174@netcom15.netcom.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Bruce Momjian wrote:
> That is also an excellent idea. Just convert their escape to \ inside
> the parser. Of course, they still have to use \\ to get a \, as in any
> string. Great idea.
You can even make it fully compliant if you want. (There are of course
backward compatibility problems. I'm not sure what the Postgres policy is
on this.)
- If the escape character is backslash, do nothing.
- Otherwise, turn all backslashes in the string to double backslashes.
- If the escape character is not set, stop here.
- Turn all occurences of the escape character into a backslash except
where the escape character is doubled, where it should be made into a
single occurence.
(Optionally, if "\n" is just an 'n' character, you can handle double
occurences of the escape character by turning the first one into a
backslash.)
Probably the best bet for PostgreSQL programmers is to always code Like
clauses with an ESCAPE '\' (or however its written).
I really wish they'd chosen a character other than underscore for the
"match one" wildcard... Is there any standard practice for seperating words
in table names?
-Z-
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-03-16 23:03:58 | Re: [SQL] How match percent sign in SELECT using LIKE? |
Previous Message | Bruce Momjian | 1999-03-16 22:26:09 | Re: [SQL] How match percent sign in SELECT using LIKE? |