Re: Per-column collation, work in progress

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Per-column collation, work in progress
Дата
Msg-id 1285307875.27917.26.camel@vanquo.pezone.net
обсуждение исходный текст
Ответ на Re: Per-column collation, work in progress  (Itagaki Takahiro <itagaki.takahiro@gmail.com>)
Ответы Re: Per-column collation, work in progress  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On fre, 2010-09-24 at 09:32 +0900, Itagaki Takahiro wrote:
> On Wed, Sep 22, 2010 at 10:29 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> >> We could support it also on MSVC.
> >> http://msdn.microsoft.com/en-us/library/a7cwbx4t(v=VS.90).aspx -- _strcoll_l
> >> http://msdn.microsoft.com/en-us/library/45119yx3(v=VS.90).aspx -- _towupper_l
> >
> > Great.
> 
> If we support both glibc and msvc, how to we handle CREATE TABLE DDLs
> in pg_dump? Since collation names depend on platforms, a backup dumped
> at UNIX cannot be reloaded to Windows. We might need to normalize
> locale names to generate a portable dump.

It is not necessary that the SQL collation names are the same as the OS
locale names.  That is just a convenient way to initialize it.  If you
need to transport dumps, you can create your own SQL collation entry at
the target that locally fits what you are trying to do (or perhaps
rename the collation at the source).

I don't think there is a universally applicable way to "normalize"
locale names, because we want to support user-defined OS locales.




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: snapshot generation broken
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: Per-column collation, work in progress