Re: Regular expression. How to disable ALL meta-character - Mailing list pgsql-general

From Chris Travers
Subject Re: Regular expression. How to disable ALL meta-character
Date
Msg-id 4266CE96.5040803@metatrontech.com
Whole thread Raw
In response to Re: Regular expression. How to disable ALL meta-character  (David Gagnon <dgagnon@siunik.com>)
List pgsql-general
David Gagnon wrote:

>
>>
>>
>>
>>
> Maybe there is a simple way to to this but I want find string X in
> different column.  The search must not be case sensitive.
>
> So that searching "aBc" in  "abcDef" return true.  I don't want
> META-CHaracter.  Or at least I don't want meta-character to cause
> errors (i.e.: No
>
Ok, how about a better way to do this?

select * from mytable where lower(mycol) LIKE lower("%" || lower(X) || "%");

Does this work?  It seems that this may be the best way to handle this
sort of thing.

Best Wishes,
Chris Travers
Metatron Technology Consulting

> ERROR:  invalid regular expression: brackets [] not balanced.
>
>
>
> Thanks for your help
> /David
>
>
>
>
>
>
>
>
>>> I found this in the manual .. but haven't found example :-(:
>>> : ....with ***=, the rest of the RE is taken to be a literal string,
>>> with all characters considered ordinary characters.
>>>
>>
>>
>> Read again the entire sentence, especially the first few words:
>>
>>  If an RE begins with ***=, the rest of the RE is taken to be a
>>  literal string, with all characters considered ordinary characters.
>>
>> Here are some examples:
>>
>> SELECT 'test string' ~ 'test[*';
>> ERROR:  invalid regular expression: brackets [] not balanced
>>
>> SELECT 'test string' ~ '***=test[*';
>> ?column? ----------
>> f
>> (1 row)
>>
>> SELECT 'test[* string' ~ '***=test[*';
>> ?column? ----------
>> t
>> (1 row)
>>
>>
>>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
>


Attachment

pgsql-general by date:

Previous
From: Rob Stone
Date:
Subject: List of Functions
Next
From: "Ben Trewern"
Date:
Subject: Re: CURRENT_TIMESTAMP vs actual time