"Peter Eisentraut" <peter_e(at)gmx(dot)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.
Ask me about EnterpriseDB's Slony Replication support!
In response to
pgsql-hackers by date
|Next:||From: Asko Oja||Date: 2008-07-29 10:56:19|
|Subject: Re: [PATCH] "\ef <function>" in psql|
|Previous:||From: Stephen R. van den Berg||Date: 2008-07-29 10:55:04|
|Subject: Relicensed and downloadable (Re: Protocol 3, Execute, maxrows to return, impact?)|