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

Re: UTF-8 support

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: sa_mokho(at)alcor(dot)concordia(dot)ca
Cc: jm(dot)poure(at)freesurf(dot)fr, pgsql-odbc(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: UTF-8 support
Date: 2001-09-24 02:47:31
Message-ID: 20010924114731R.t-ishii@sra.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-odbc
> > 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.

You are correct. We don't need how=3.

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

I don't quite understand your question. What I thought were something
like this:

SELECT pg_available_encodings();
pg_available_encodings
----------------------
SQL_ASCII
EUC_JP
EUC_CN
EUC_KR
EUC_TW
UNICODE
MULE_INTERNAL
LATIN1
LATIN2
LATIN3
LATIN4
LATIN5
KOI8
WIN
ALT
SJIS
BIG5
WIN1250

BTW, another question comes to my mind. Why don't we make available
this kind of information by ordinaly tables or views, rather than by
functions?  It would be more flexible and easy to use.
--
Tatsuo Ishii

In response to

Responses

pgsql-hackers by date

Next:From: Kevin WayDate: 2001-09-24 02:51:50
Subject: Re: Bug?: Update on ancestor for a row of a child
Previous:From: Marc G. FournierDate: 2001-09-24 02:39:32
Subject: Re: Beta time

pgsql-odbc by date

Next:From: Serguei MokhovDate: 2001-09-24 03:05:17
Subject: Re: UTF-8 support
Previous:From: Serguei MokhovDate: 2001-09-24 02:15:26
Subject: Re: UTF-8 support

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