Re: pg_database encoding again
От | Christopher Kings-Lynne |
---|---|
Тема | Re: pg_database encoding again |
Дата | |
Msg-id | 135201c328c0$1a780150$6500a8c0@fhp.internal обсуждение исходный текст |
Ответ на | pg_database encoding again ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>) |
Ответы |
Re: pg_database encoding again
|
Список | pgsql-hackers |
> That sounds about right. If you're using databases of different > encodings in the same installation, it would probably be wise to > restrict yourself to the intersection of those encodings when choosing > database names. Bummer. So there's no one encoding I can set it to :( Actually, since the phpPgAdmin interface only allows the creation of databases via the create database screen, could we just always set it to the encoding of template1? How do I get the encoding of the server? Is that the same as the encoding of template1? > I agree that this isn't ideal, but I don't see any way to improve it. > If you like, we could put in code to *enforce* a restriction to 7-bit > ASCII in database names (and user and group names too) ... but that > doesn't seem like a big improvement. I would suggest force Unicode... Chris
В списке pgsql-hackers по дате отправления: