From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Nicola Cisternino <ncister(at)tiscali(dot)it> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: String comparision in PostgreSQL |
Date: | 2012-08-29 15:08:21 |
Message-ID: | CAHyXU0zrMgadjRV8=DG68LxH9oJbLh7Z2C9+5tKZ4LcAqTgyTQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Aug 28, 2012 at 9:46 AM, Nicola Cisternino <ncister(at)tiscali(dot)it> wrote:
> Hi all,
> I'm valutating a complex porting of our application based on Sybase
> SqlAnywhere on PostgreSQL (I've love it ...) and I'd like to have your
> opinion about searching/ordering funcionality.
> The problem is about string comparision.
> MS Sql server, MySql, SqlAnywhere and other DB engine allow a simple
> definition of case sensitive/insensitive behavior using char, varchar and
> text field type.
> In PostgreSQL I've already tried to use "citext", lower() function (applied
> to indexes, too ...), ILIKE an so on ..... but nothing really work as I need
> (poor performances ...) !!
hm, poor performance? can you elaborate?
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | salah jubeh | 2012-08-29 15:12:23 | Re: using vars in ddl in procedure call |
Previous Message | Gauthier, Dave | 2012-08-29 14:56:45 | using vars in ddl in procedure call |