Re: [WIP] patch - Collation at database level - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: [WIP] patch - Collation at database level
Date
Msg-id 87fxpt3qni.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: [WIP] patch - Collation at database level  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
"Peter Eisentraut" <peter_e@gmx.net> writes:

> In my opinion, you are starting this project from the wrong end.  I would 
> suggest you approach it like this:
>
> - Find some collation implementations
> - Patch PostgreSQL to link with them

Well I think the feeling is that we may as well start with the lowest common
denominator of libc's collation implementation. It's the only one everyone's
going to have. Later adding compile-time options to use a different library
and different function calls might be useful but a lot of people are unhappy
about the idea of *requiring* a major outside library for this.

> - Patch PostgreSQL to apply them for comparison

Er, yes. Well we do that already but the tricky bit is keeping track of
multiple collations and applying the right one for each comparison.

So we do need the concept of multiple collations and the syntax to select a
collation for each ordering operation.



--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication
support!


pgsql-hackers by date:

Previous
From: "Asko Oja"
Date:
Subject: Re: [PATCH] "\ef " in psql
Next
From: Stephen Frost
Date:
Subject: Re: patch: Add a separate TRUNCATE permission