Re: character encoding in StartupMessage
От
Christopher Kings-Lynne
Тема
Re: character encoding in StartupMessage
Дата
Msg-id
4403F185.2030808@familyhealth.com.au
Ответ на
Re: character encoding in StartupMessage (Tom Lane)
Список
Дерево обсуждения
character encoding in StartupMessage John DeSoi <desoi@pgedit.com>
Re: character encoding in StartupMessage Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: character encoding in StartupMessage Tom Lane <tgl@sss.pgh.pa.us>
Re: character encoding in StartupMessage John DeSoi <desoi@pgedit.com>
Re: character encoding in StartupMessage Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: character encoding in StartupMessage Martijn van Oosterhout <kleptog@svana.org>
Re: character encoding in StartupMessage Tom Lane <tgl@sss.pgh.pa.us>
Re: character encoding in StartupMessage Alvaro Herrera <alvherre@commandprompt.com>
Re: character encoding in StartupMessage Martijn van Oosterhout <kleptog@svana.org>
Re: character encoding in StartupMessage Tom Lane <tgl@sss.pgh.pa.us>
Re: character encoding in StartupMessage John DeSoi <desoi@pgedit.com>
Re: character encoding in StartupMessage Tom Lane <tgl@sss.pgh.pa.us>
Re: character encoding in StartupMessage Martijn van Oosterhout <kleptog@svana.org>
> I don't see any very nice solution at the moment. Once we get support > for per-column locales, it might be possible to declare that the shared > catalogs are always in UTF8 encoding and get the necessary > conversions to happen automatically. At the very least, could we always convert dbnames and store them as their own encoding? That way at least in HTML you can probably mark them out as having particular encodings or something... Chris
В списке pgsql-hackers по дате отправления
