some encodings aren't supported

From: Quan Zongliang <quanzongliang(at)gmail(dot)com>
To: pgadmin-hackers(at)postgresql(dot)org(dot)
Subject: some encodings aren't supported
Date: 2009-11-23 00:16:35
Message-ID: 20091123070039.8D5E.4125B4E5@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi

And, 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(")"));

-----------------------------------------------
Quan Zongliang
quanzongliang(at)gmail(dot)com

Attachment Content-Type Size
dlgDatabase.patch application/octet-stream 508 bytes
pgConn.patch application/octet-stream 506 bytes

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message pgAdmin Trac 2009-11-23 09:03:43 Re: [pgAdmin III] #101: New VACUUM options syntax
Previous Message pgAdmin Trac 2009-11-22 22:09:09 Re: [pgAdmin III] #14: Save graphical explain output