[pgAdmin III] #103: some encodings aren't supported
От | pgAdmin Trac |
---|---|
Тема | [pgAdmin III] #103: some encodings aren't supported |
Дата | |
Msg-id | 055.13a6c88d29307d3903377a4c09d11155@code.pgadmin.org обсуждение исходный текст |
Ответы |
Re: [pgAdmin III] #103: some encodings aren't supported
Re: [pgAdmin III] #103: some encodings aren't supported Re: [pgAdmin III] #103: some encodings aren't supported |
Список | pgadmin-hackers |
#103: some encodings aren't supported ----------------------------+----------------------------------------------- Reporter: Quan Zongliang | Owner: dpage Type: bug | Status: new Priority: minor | Milestone: Component: pgadmin | Version: trunk Keywords: encoding | Platform: ----------------------------+----------------------------------------------- some encodings aren't supported by PostgreSQL yet: BIG5, GB18030, GBK, JOHAB, SJIS, SHIFT_JIS_2004, UHC See here: http://www.postgresql.org/docs/8.4/static/multibyte.html But all of them can be selected in new Database dialog. I checked some PostgreSQL sources. some functions are defined in: backend/utils/mb/encnames.c pg_valid_server_encoding_id can check whether an enconding is supported by server. It invoke macro PG_VALID_BE_ENCODING. And it is included in libpq-fe.h Patches are attached. I didn't define pg_encoding_to_char function in pgConn class. dlgDatabase is still invoke connection->ExecuteScalar(wxT("SELECT pg_encoding_to_char(") + NumToStr(encNo) + wxT(")")); -- Ticket URL: <http://code.pgadmin.org/trac/ticket/103> pgAdmin III <http://code.pgadmin.org/trac/> pgAdmin III
В списке pgadmin-hackers по дате отправления: