From: | "Aaron Bono" <postgresql(at)aranya(dot)com> |
---|---|
To: | "Mario Splivalo" <mario(dot)splivalo(at)mobart(dot)hr>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Postgres regexp matching failure? |
Date: | 2006-09-05 16:10:16 |
Message-ID: | bf05e51c0609050910k226fe36frbbfbe14db34a6b9d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On 9/5/06, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
>
>
> In Perl at least, \b is a word boundary. In PostgreSQL (and probably
> Tcl as well) it's a backslash AFAICT.
More specifically, Perl, Java and Python interpret \b as a backspace in the
Character class only (got that from the Regular Expression pocket reference)
but otherwise are word boundries. I am not entirely sure what the Character
class context is referring to but it does show that \b is interpreted
differently under different contexts. PostgreSQL may not have a way (or at
least a very good way) to make this distinction.
Any other thoughts?
==================================================================
Aaron Bono
Aranya Software Technologies, Inc.
http://www.aranya.com
http://codeelixir.com
==================================================================
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2006-09-06 03:51:00 | Way to reverse ordering of an IP ... ? |
Previous Message | codeWarrior | 2006-09-05 16:07:36 | Re: Subquery alternatives? |