| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Albert Vilà <albvil(at)gmail(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Problem with postgres and Suse |
| Date: | 2004-09-14 10:41:39 |
| Message-ID: | Pine.BSO.4.56.0409140537510.18601@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Tue, 14 Sep 2004, [ISO-8859-1] Albert Vilà wrote:
> With build 215 and Debian all it's ok
>
> Now with suse and 215 the problem is :
>
> java.lang.Exception: 0 - - Invalid character data was found. This is
> most likely caused by stored data containing characters that are
> invalid for the character set the database was created in. The most
> common example of this is storing 8bit data in a SQL_ASCII database.
Yes, but this is different stacktrace than you initially showed. The
error message seems clear. What is the encoding of your database? It
appears not to be set correctly for your data. The JDBC driver (unlike
most other client interfaces) requires your data to be encoded correctly.
Unfortunately the only way to fix it is a dump and reload.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Penhey | 2004-09-14 14:30:33 | Problem with dollar-quoted CREATE OR REPLACE FUNCTION |
| Previous Message | Kris Jurka | 2004-09-14 10:26:20 | Re: Problem with postgres and Suse |