Re: Is this error correct/possible?

Joost Kraaijeveld <J.Kraaijeveld@Askesis.nl> writes:

> I have a database which is created in PostgreSQL 8.0.3 which is filled
> with a PostgreSQL 7.4.7 database backup. Both databases where created
> with SQL_ASCII.
>
> Running a query against on of the tables gives this error (with the
> pg74.216.jdbc3.jar and postgresql-8.0-312.jdbc3.jar drivers):
>
> "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."

Could you copy/paste the complete exception and stacktrace?


> Inspection of the row (using pgadmin3) shows that there is the char "ü"
> in a char(40) columns.
>
> Questions:
>
> 1. Is a "ü" allowed in a SQL_ASCII database and a column of char(40)?

From a very recent discussion on pgsql-Odbc (check the archive), it is
not allowed. Not allowed "anymore" from what I got. Which is quite
sensible considering that ü is not ASCII: how would you sort it, upper
it, etc.? I did not get if this has been recently enforced by the ODBC
driver, the engine, both... check the archive.


> 2. If so, is this a JDBC bug?

The stacktrace and such debug stuff would help tracking what JDBC is
doing here.


> 3. If not, is this a PostgreSQL bug, allowing a non-allowed character in
> a column?

Maybe it was allowed in 747, not anymore in 8.0.3 ?