| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | emilu(at)encs(dot)concordia(dot)ca |
| Cc: | Emre Hasegeli <hasegeli(at)tart(dot)com(dot)tr>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: where col1 not ilike ('str1%', 'str2%'... 'strN%') support? |
| Date: | 2011-08-31 16:16:02 |
| Message-ID: | CAFj8pRBotEwp-0t0Ys=zww=dkSWRT1ESdHn=ZkFBvgWY+LGKZQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
2011/8/31 Emi Lu <emilu(at)encs(dot)concordia(dot)ca>:
> On 08/31/2011 03:16 AM, Emre Hasegeli wrote:
>>
>> 2011/8/30 Emi Lu<emilu(at)encs(dot)concordia(dot)ca>:
>>
>>> First, where not (col1 ~~* any(array['str1%', 'str2%'... 'strN%'])) will
>>> work for me.
>>>
>>> But I feel " ilike ('str1', ... 'strN')" is more intuitive, isn't it?
>>
>> It is not. It is like "where id = (3, 5, 7)".
>
>
> What I mean is ilike ('%str1%', ... '%strN%')
>
> I just forgot to put %
it useless to introduce non SQL feature where some native feature exists now.
Regards
Pavel Stehule
>
> Emi
>
> --
> Sent via pgsql-sql mailing list (pgsql-sql(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-sql
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Viktor Bojović | 2011-08-31 21:27:29 | function based index problem |
| Previous Message | lxnf98mm | 2011-08-31 13:26:57 | ERROR: cannot subscript type text because it is not an array |