Skip site navigation (1) Skip section navigation (2)

Re: UTF-8 support

From: "Serguei Mokhov" <sa_mokho(at)alcor(dot)concordia(dot)ca>
To: <jm(dot)poure(at)freesurf(dot)fr>, "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>
Cc: <pgsql-odbc(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: UTF-8 support
Date: 2001-09-24 02:15:26
Message-ID: 001d01c1449e$d2074d60$5dd9fea9@gunn (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-odbc
----- Original Message ----- 
From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Sent: Sunday, September 23, 2001 7:58 PM

> > 3) Is there a way to query available encodings in PostgreSQL for display in 
> > pgAdmin.
> > Is it a planned feature in PostgreSQL 7.2? This would be nice if it existed.
> > Example: function pg_available_encodings -> SQL-ASCII;UNICODE;EUC-JP etc...
> 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?

        3: returns encodings of both backend and frontend

Why both? To compare and match upon the need.
If by 0 (ALL) you meant the same, then please ignore my comment.

My question is now how many BE's/FE's would you return encodings for?


In response to


pgsql-hackers by date

Next:From: Marc G. FournierDate: 2001-09-24 02:38:08
Subject: Re: CVS changes
Previous:From: Alex PilosovDate: 2001-09-24 01:29:11
Subject: outer joins strangeness

pgsql-odbc by date

Next:From: Tatsuo IshiiDate: 2001-09-24 02:47:31
Subject: Re: UTF-8 support
Previous:From: Hiroshi InoueDate: 2001-09-24 00:48:00
Subject: Re: New driver options in 7.01.0007

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group