> I'd be inclined to handle it similarly to the way that Tatsuo did with
> conversion_procs: let collations be represented by comparison functions
> that meet some suitable API. I think that trying to represent such a
> table as an SQL table compactly will be a nightmare, and trying to
> access it
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I am trying to figure out which is the best way to store custom collation
> tables on a PostgreSQL server system, and what kind of interface to
> provide to users to allow them to create their own.
> A collation table essentially consists of a mapping
On Mon, 18 Nov 2002, Peter Eisentraut wrote:
> A collation table essentially consists of a mapping 'character code ->
> weight' for every character in the set and some additional considerations
> for one-to-many and many-to-one mappings, plus a few feature flags.
>
> How would a user go about cre
I am trying to figure out which is the best way to store custom collation
tables on a PostgreSQL server system, and what kind of interface to
provide to users to allow them to create their own.
A collation table essentially consists of a mapping 'character code ->
weight' for every character in th
