From: | hamann(dot)w(at)t-online(dot)de |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: non-static LIKE patterns |
Date: | 2012-04-12 06:35:18 |
Message-ID: | 4F8677A6.mailxFT71K7US2@amadeus3.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
patrick keshishian <pkeshish(at)gmail(dot)com> writes:
> Thanks for the quick reply. Would be tough choosing another
> "reasonable" ESCAPE character while dealing with paths. Will think
> more about this.
If you want it to be bulletproof, what I'd think about is something like
WHERE second.path LIKE quote_like(first.path)||'%'
where quote_like() is a function that inserts a backslash before each
backslash, percent, and underscore in the given value. Probably not
hard to cons that up from regexp_replace().
regards, tom lane
Just out of curiosity: wouldn't that (as well as using non-static like)
be an enormous performance problem?
I tried something with normal "~" regex matching some time ago but
gave up on the idea pretty soon
Regards
Wolfgang Hamann
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Guettler | 2012-04-12 08:16:22 | Value to long for type ....: Columnname missing |
Previous Message | Albretch Mueller | 2012-04-12 04:51:17 | Any information about the PostgreSQL Certified Engineer program? |