From: | Charles Curley <charles(dot)h(dot)curley(at)lmco(dot)com> |
---|---|
To: | pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: [GENERAL] Case insensitive "contains" search |
Date: | 1998-11-09 18:12:16 |
Message-ID: | 3647307F.17FDF8B3@lmco.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ulf Mehlig wrote:
> In my opinion, the regexps are much more powerfull compared to "like
> '%anything'"-statements; but the regular expression syntax is a little
> bit weird, and if you have a look in the docs of programs which
> heavily depend on regexps (perl, grep, emacs, ...) you'll find some
> nice annoying little differences in "to-quote-or-not-to-quote"
> sections ...
Is there a text that describes the RE usage in PostgrSQL? I'd like to know
how to do more complicated expressions, like, "^(((charl|jam)es)|(bob))",
which should match a field that begins with "charles", "james", or "bob".
Yes, it can be rewritten, but I have yet to see a demo of how to use
parenthetical RE's in PostgreSQL. What I want to do is provide the user
with the ability to use RE's ala egrep. It would be really sweet to see
perl RE's in there. I've written a couple of times about this and I've
gotten answer as to how to rewrite a particular RE to work with
PostgreSQL, but I would like a more general description. Can the backend
be easily linked with a different regexp library like GNU's? BTW, all of
my comments are referencing 6.3.2.
--
Charles Curley, Staff Engineer
Computer Integrated Manufacturing
Lockheed Martin Ocala Operations
From | Date | Subject | |
---|---|---|---|
Next Message | David Hartwig | 1998-11-09 18:37:33 | Re: [GENERAL] postgreSQL 6.3.2 and AIX |
Previous Message | Gene Selkov, Jr. | 1998-11-09 17:58:46 | is NULL = NULL true or false? |