From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Per-column collation, proof of concept |
Date: | 2010-07-15 03:57:08 |
Message-ID: | AANLkTimPLCtsqgYJiAbezFNybkbQxVr2NKQEJyVLFbhK@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/7/14 Peter Eisentraut <peter_e(at)gmx(dot)net>:
> On ons, 2010-07-14 at 19:35 +0200, Pavel Stehule wrote:
>> I have only one question - If I understand well you can use collate
>> just for sort. What is your plan for range search operation?
>
> My patch does range searches. Sorting uses the same operators, so both
> will be supported. (Sorting is not yet implemented, as I had written.)
>
>> Sort is
>> interesting and I am sure important for multilangual applications, for
>> me - more important is case sensitive, case insensitive, accent
>> sensitive, insensitive filtering - do you have a plan for it?
>
> You may be able to do some of these by using appropriate locale
> definitions. I'd need some examples to be able to tell for sure.
>
>> what about DISTINCT clause, maybe GROUP BY clause ?
>
> DISTINCT and GROUP BY work with equality, which is not affected by
> locales (at least under the current rules).
>
:( maybe we have to enhance a locales - or do some work in this way.
In Czech's IS is relative often operation some like
name = 'Stěhule' COLLATION cs_CZ_cs_ai -- compare case insensitive
accent insensitive
PostgreSQL is last db, that doesn't integreated support for it
Regards
Pavel
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2010-07-15 05:30:46 | Re: standard_conforming_strings |
Previous Message | Robert Haas | 2010-07-15 02:49:45 | Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore |