From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, marcin mank <marcin(dot)mank(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Per-column collation |
Date: | 2010-11-17 05:07:33 |
Message-ID: | AANLkTimtiDXy9M98YXyrX_fihsMiyFrZujjD_Z51Up0L@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/11/16 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Martijn van Oosterhout <kleptog(at)svana(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-11-17 05:36:00 | Re: Adding nullable indicator to Describe |
Previous Message | Chris Forno | 2010-11-17 05:01:57 | Adding nullable indicator to Describe |