datname datdba encoding datpath
------------------------------------------------
courses 26 7 courses
I have tested with LATIN1 - LATIN5 and I haven't got any result...
I'd need the Spanish 'ñ' (that is what I insert)...
Maybe I need to insert this character in a special way? The client is
set to the same encoding as the database is.
Thanks,
Rosa M. Carro
P.S. Could it be related to multibyte (or something similar)?
Tatsuo Ishii wrote:
> > I have defined a database with the encoding SQL_ASCII. I fill the
> > database by using embedded SQL. When I insert the value "Señales", it is
> > correctly inserted. I read the correct value by typing the query in
> > postgres, but when I access this database from a Java program, via JDBC,
> > I obtain the value "Seqales". The LANG variable is set to "es_ES"
> > (spanish) which I suppose is OK.
> >
> > I have changed this database encoding to LATIN1 and set the client
> > characterset to LATIN1 by typing \encoding LATIN1.
> >
> > Now when I access the data from postgres interface I obtain
> > "Se(82f1)ales", and when I get the value through the Java program, I
> > obtain
> > "Se ñales".
> >
> > Does anybody knows what is happening? Where can I find information
> > about this?
> > Thanks in advance,
> > Rosa M. Carro
>
> (82f1) is 0x82 (leading character for LATIN2) + 0xf1 (Spanish 'n'), that is
> the intermediate representation in the backend when the encoding translatin
> is necessary. My guess is you set the database encoding to LATIN2, not
> LATIN1. Can you show me the result of the query:
>
> select * from pg_database;
> --
> Tatsuo Ishii
