Re: character encoding in StartupMessage - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: character encoding in StartupMessage
Date
Msg-id 4403DD34.8020709@familyhealth.com.au
Whole thread Raw
In response to character encoding in StartupMessage  (John DeSoi <desoi@pgedit.com>)
Responses Re: character encoding in StartupMessage
List pgsql-hackers
> I could not find anything in the Frontend/Backend protocol docs about 
> character encoding in the StartupMessage. Assuming it is legal for a 
> database or user name to have unicode characters, how is this handled 
> when nothing yet has been said about the client encoding?

A similar badness is that if you issue CREATE DATABASE from a UTF8 
database, the dbname will be stored as UTF8.  Then, if you go to a 
LATIN1 database and create another it will be stored as LATIN1.

Then, it's impossible to display both database names on the same screen 
or webpage as they have different encodings...  Not only that but it's 
impossible to know what encoding it IS in since it's the encoding of the 
database from where you issued the CREATE DATABASE instruction from, not 
the encoding of the database itself.

Chris




pgsql-hackers by date:

Previous
From: John DeSoi
Date:
Subject: character encoding in StartupMessage
Next
From: Tom Lane
Date:
Subject: Re: Dead Space Map