Re: Client_encoding

Le 23/12/2010 15:14, Mark Watson a écrit :
> Hello group,
> Any suggestions as to how to fix this are greatly appreciated.
> My setup is Vista, locally installed Postgres 8.4.6 in default folders with
> db initialised as (server_encoding) UTF8, and databases created with default
> encoding of WIN1252. My application program is behaving correctly using
> libpq.dll. pgAdmin is configured with Preferences=>Font = Tahoma
> windows-1252 and Query=>Font = Tahoma 9 windows-1252.
>
> The test case:
> 1. Create a text file test.txt containing 1 line of 2 characters: éÉ (acute
> accented lowercase and uppercase e, hex(E9C9), valid win1252 characters.
> 2.
> CREATE DATABASE dbtest
> WITH OWNER = postgres
> ENCODING = 'WIN1252'
> TABLESPACE = pg_default
> LC_COLLATE = 'French_Canada.1252'
> LC_CTYPE = 'French_Canada.1252'
> CONNECTION LIMIT = -1;
> 3. Open query window to database dbtest and import the file test.txt...
> 4.
> CREATE TABLE test
> (
> col_descr text
> )
> WITH (
> OIDS=FALSE
> );
> ALTER TABLE test OWNER TO postgres;
> set client_encoding = 'WIN1252';
> COPY test FROM 'C:\\pgtemp\\test.txt' with delimiter as '|' csv;
> select * from test;
> 5. Results (no errors reported):
> --- col_descr
> -- ----------------
> -- (1 row with nothing displayed, but the length of
> col_descr = 2)
> 6. If I execute the query:
> set client_encoding = 'UTF8';
> select * from test;
>
> The correct results are displayed.
>
> Is there a way, in PgAdmin, to to display the results when client_encoding
> is set to WIN1252 ?
>

Nope. The Font option in the Preferences tab doesn't set the font of the
grid. It'll do on next pgAdmin (major) release.

--
Guillaume
http://www.postgresql.fr
http://dalibo.com