From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "'Tatsuo Ishii'" <t-ishii(at)sra(dot)co(dot)jp>, jm(dot)poure(at)freesurf(dot)fr |
Cc: | pgsql-odbc(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] UTF-8 support |
Date: | 2001-09-27 15:00:41 |
Message-ID: | AA30E7BCCA5C1D4E88A231900F8325C00B34@dogbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-odbc |
> -----Original Message-----
> From: Tatsuo Ishii [mailto:t-ishii(at)sra(dot)co(dot)jp]
> Sent: 24 September 2001 00:58
> To: jm(dot)poure(at)freesurf(dot)fr
> Cc: pgsql-odbc(at)postgresql(dot)org; pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [ODBC] [HACKERS] UTF-8 support
>
> Currently no. But it would be easy to implement such a
> function. What comes in mind is:
>
> pg_available_encodings([INTEGER how]) RETURNS setof TEXT
>
> where how is
>
> 0(or omitted): returns all available encodings
> 1: returns encodings in backend
> 2: returns encodings in frontend
>
> Comments?
Would certainly be useful to pgAdmin if someone could implement this...
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Karel Zak | 2001-09-27 15:26:56 | Re: Problem with setlocale (found in libecpg) [accessing a memory location after freeing it] |
Previous Message | Tom Lane | 2001-09-27 14:09:13 | Re: multibyte performance |
From | Date | Subject | |
---|---|---|---|
Next Message | Robinson, Chad | 2001-09-27 15:05:58 | Re: Locking timeouts |
Previous Message | Hiroshi Inoue | 2001-09-27 09:28:04 | Re: Locking timeouts |