On Thu, Aug 30, 2012 at 9:34 AM, Scott Marlowe wrote:
> On Thu, Aug 30, 2012 at 6:09 AM, F. BROUARD / SQLpro
> wrote:
>> Le 30/08/2012 12:45, Craig Ringer a écrit :
>>
>>
>>> That's my understanding, but I don't know which other database systems
>>> you're talking about because you've never speci
On Thu, Aug 30, 2012 at 6:09 AM, F. BROUARD / SQLpro
wrote:
> Le 30/08/2012 12:45, Craig Ringer a écrit :
>
>
>> That's my understanding, but I don't know which other database systems
>> you're talking about because you've never specifically named any.
>>
> In his primary post he talk about SQL Se
Le 30/08/2012 12:45, Craig Ringer a écrit :
That's my understanding, but I don't know which other database systems
you're talking about because you've never specifically named any.
In his primary post he talk about SQL Server, Sybase and MySQL wich does
good jobs with collation
Almost a
On 08/30/2012 06:54 PM, Nicola Cisternino wrote:
At this point, the solution could be a new, custom, operating system
collation (something like: en_CI_US.UTF-8)
As far as I know - and as I said, I'm hardly an expert in Pg's guts -
there's no way to create a case insensitive collatio
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 . is it right ?
That
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 . is it right ?
That's my understanding, but I don't know which oth
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 only added rel
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 intended) there's an index that's
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 only added relatively
recently - in 9.1, by the looks:
On Wed, Aug 29, 2012 at 10:56 AM, Nicola Cisternino wrote:
> 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
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 intended) there's an index that's being
used in one case and not in the other.
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 searching/ordering funcional
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 searching/ordering funcionality.
> The problem is about string comparis
13 matches
Mail list logo
