----- Original Message -----
From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Sent: Sunday, September 23, 2001 10:47 PM
> > 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();
Which ones belong to the backend and which ones to the frontend?
Or even more: which ones belong to the backend, which ones
to the frontend #1, which ones to the frontend #2, etc...
For examle, I have two fronends:
FE1: UNICODE, WIN1251
FE2: KOI8, UNICODE
BE: UNICODE, LATIN1, ALT
Which ones SELECT pg_available_encodings(); will show?
The ones of the BE and the FE making the request?
In case I need to communicate with BE using one common
encoding between the two if it is available.
> 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.
Sounds like a good idea, make another system table for encodings
and NLS stuff...
In response to
pgsql-hackers by date
|Next:||From: bpalmer||Date: 2001-09-24 04:18:49|
|Subject: LOCAL_CREDS -> SCM_CREDS in src/backend/libpq/auth.c:535|
|Previous:||From: Hiroshi Inoue||Date: 2001-09-24 03:01:54|
|Subject: Re: an already existing alter table drop column ?!?!?!|
pgsql-odbc by date
|Next:||From: Hiroshi Inoue||Date: 2001-09-24 05:25:49|
|Subject: Re: [ODBC] UTF-8 support|
|Previous:||From: Tatsuo Ishii||Date: 2001-09-24 02:47:31|
|Subject: Re: UTF-8 support|