| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | "Allan Huffman" <huffmana(at)ppc(dot)pims(dot)org> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Re: PostgreSQL Help |
| Date: | 1999-10-11 14:04:22 |
| Message-ID: | 199910111404.XAA00901@ext16.sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Dear Tatsuo (did I get your name right this time),
Yes:-)
> After installing PostgreSQL 6.5.2
> --with-mb=UNICODE
>
> I am still getting a truncation of some varchar columns. When accessing a table
> in PostgreSQL I get this:
> $(C(BERROR: Conversion between UNICODE and SQL_ASCII is not supported$(D(B
What kind of client program are you using? If it's psql or something
using libpq, you are likely setting an environment variable
PGCLIENTENCODING to SQL_ASCII. As the message said, Conversion between
UNICODE and SQL_ASCII is not currently supported. You should unset the
variable and use a client program that understands UNICODE (UTF-8).
If your client program is a Java using JDBC, I have no idea at all
since I am not involved into the PostgreSQL JDBC driver.
---
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Weinberg | 1999-10-11 14:57:16 | Re: [HACKERS] memory problems in copying large table to STDOUT |
| Previous Message | Bruce Momjian | 1999-10-11 13:46:17 | Re: [HACKERS] Interesting Quote you might enjoy about PGSQL. |