Tom Lane wrote: patrick keshishian <pkeshish@xxxxxxxxx> 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 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
