From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Quan Zongliang <quanzongliang(at)gmail(dot)com> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: some encodings aren't supported |
Date: | 2009-11-23 11:24:57 |
Message-ID: | 937d27e10911230324r58c79749m195cf51a9290c0d0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Thanks - committed.
On Mon, Nov 23, 2009 at 9:16 AM, Quan Zongliang <quanzongliang(at)gmail(dot)com> wrote:
> 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
>
>
> --
> Sent via pgadmin-hackers mailing list (pgadmin-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-hackers
>
>
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | pgAdmin Trac | 2009-11-23 18:47:52 | [pgAdmin III] #103: some encodings aren't supported |
Previous Message | svn | 2009-11-23 11:24:39 | SVN Commit by dpage: r8087 - in branches/REL-1_10_0_PATCHES/pgadmin3: . pgadmin/dlg pgadmin/include/db |