Re: String comparision in PostgreSQL
От | Nicola Cisternino |
---|---|
Тема | Re: String comparision in PostgreSQL |
Дата | |
Msg-id | 503E3B91.2040107@tiscali.it обсуждение исходный текст |
Ответ на | Re: String comparision in PostgreSQL (Merlin Moncure <mmoncure@gmail.com>) |
Ответы |
Re: String comparision in PostgreSQL
Re: String comparision in PostgreSQL |
Список | pgsql-general |
Il 29/08/2012 17.08, Merlin Moncure ha scritto:
The same query using " .... LIKE <value> ...." is completed in 15 ms while using " .... ILIKE <value> ...." the execution time is 453 ms ....On Tue, Aug 28, 2012 at 9:46 AM, Nicola Cisternino <ncister@tiscali.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
В списке pgsql-general по дате отправления: