[GENERAL] String comparision in PostgreSQL

2012-08-29 Thread Nicola Cisternino
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

Re: [GENERAL] String comparision in PostgreSQL

2012-08-29 Thread Nicola Cisternino
Il 29/08/2012 17.08, Merlin Moncure ha scritto: On Tue, Aug 28, 2012 at 9:46 AM, Nicola Cisternino 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 sea

Re: [GENERAL] String comparision in PostgreSQL

2012-08-30 Thread Nicola Cisternino
Il 29/08/2012 18.09, Chris Angelico ha scritto: On Thu, Aug 30, 2012 at 1:56 AM, Nicola Cisternino wrote: The same query using " LIKE " is completed in 15 ms while using " ILIKE " the execution time is 453 ms Sounds to me like (pun not intend

Re: [GENERAL] String comparision in PostgreSQL

2012-08-30 Thread Nicola Cisternino
Il 30/08/2012 4.01, Craig Ringer ha scritto: On 08/28/2012 10:46 PM, Nicola Cisternino wrote: 1) Why PostgreSQL don't use COLLATE to manage case sensitive / insensitive comparision (I think it's the best and ANSI standard way ) ? Support for per-column collations in PG was

Re: [GENERAL] String comparision in PostgreSQL

2012-08-30 Thread Nicola Cisternino
Il 30/08/2012 12.45, Craig Ringer ha scritto: On 08/30/2012 05:16 PM, Nicola Cisternino wrote: Thus the problem is that " collations are implemented using the operating system charset and locale support ... " while, other engines, implements collations internally . i