| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Per-column collation, proof of concept |
| Date: | 2010-07-14 21:11:44 |
| Message-ID: | 1279141904.30100.4.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | marcin mank | 2010-07-14 21:57:56 | Re: cross column correlation revisted |
| Previous Message | Joshua D. Drake | 2010-07-14 19:26:44 | PgWest 2010 Call for Papers! |