| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Aaron Bono" <postgresql(at)aranya(dot)com> |
| Cc: | "Postgres SQL language list" <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: Regular Expression in SQL |
| Date: | 2006-07-16 02:22:32 |
| Message-ID: | 25326.1153016552@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
"Aaron Bono" <postgresql(at)aranya(dot)com> writes:
> I thought by using the FOR '#' I could specify exactly what part of the
> expression I would get but it still grabs the first (...) of the pattern.
Hmm ... I think that this is a bug in similar_escape(): it ought to
transform parentheses in a SIMILAR pattern into non-capturing parentheses.
Until this is fixed, your best bet is to use the POSIX-regexp form of
substring(). You can't sneak non-capturing parens through
similar_escape, because it'll try to escape the ? ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nate Teller | 2006-07-17 01:09:48 | Re: How to find entries missing in 2nd table? |
| Previous Message | Aaron Bono | 2006-07-15 22:26:28 | Re: Querying for name/value pairs in reverse |