From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Jim Nasby <decibel(at)decibel(dot)org>, postgres general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: large document multiple regex |
Date: | 2007-02-02 22:01:59 |
Message-ID: | 20070202220159.GC28220@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Feb 02, 2007 at 12:00:27PM -0500, Merlin Moncure wrote:
> On 2/1/07, Jim Nasby <decibel(at)decibel(dot)org> wrote:
> >Have you thought about something like ~
> >'(first_string|second_string| third_string)'? Obviously your
> >example would be more complex, but I believe that with careful
> >crafting, you can get regex to do a lot without resorting to
> >multiple passes.
>
> that doesn't work...i researched the problem further and found that
> postgresql regex implementation has the built in limitation to quit
> scanning after the first matched group (this is noted in the
> documentation). There is no way that I can see to extract two or
> more non contiguous text chunks in a single regex.
>
> To do it properly, you need to have the sophistication of perl regex
> with it's magic variables.
It looks like that's coming in 8.3 :)
<http://archives.postgresql.org/pgsql-hackers/2007-02/msg00039.php>
Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-02-02 22:58:06 | Re: [pgsql-patches] [GENERAL] Corrupt database? 8.1/FreeBSD6.0 |
Previous Message | Mark Walker | 2007-02-02 21:52:03 | Re: Rule, update and aggregate functions |