Re: Per-column collation - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Per-column collation
Date
Msg-id AANLkTimtiDXy9M98YXyrX_fihsMiyFrZujjD_Z51Up0L@mail.gmail.com
Whole thread Raw
In response to Re: Per-column collation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2010/11/16 Tom Lane <tgl@sss.pgh.pa.us>:
> Martijn van Oosterhout <kleptog@svana.org> writes:
>> On Tue, Nov 16, 2010 at 10:32:01PM +0200, Peter Eisentraut wrote:
>>> On tis, 2010-11-16 at 21:05 +0100, marcin mank wrote:
>>>> It would be nice if we could have some mapping of locale names bult
>>>> in, so one doesn`t have to write alternative sql depending on DB
>>>> server OS:
>
>>> Sure that would be nice, but how do you hope to do that?
>
>> Given that each operating system comes with a different set of
>> collations, it seems unlikely you could even find two collations on
>> different OSes that even correspond.
>
> Yeah, the *real* portability problem here is that the locale behavior is
> likely to be different, not just the name.  I don't think we'd be doing
> people many favors by masking behavioral differences between a forced
> common name.
>

no, minimally there is same behave of cs_CZ.utf8 and cs_CZ.iso88592.
But without any "alias" user should to modify source code, when he
change a encoding.

Pavel

>                        regards, tom lane
>


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: contrib: auth_delay module
Next
From: Chris Forno
Date:
Subject: Adding nullable indicator to Describe