While I could see various multibyte issues in the archives and in the
TODO list, I couldn't spot this exact issue:
I am working with a database that uses UNICODE encoding.
I have a varchar column (col_x) that includes a mix of Chinese and
regular ASCII characters.
On PostgreSQL 7.4.13 (on RHEL4) "select col_x, upper(col_x) from
my_table" performs the desired upper() conversion - i.e. the ASCII
characters are converted to upper case and the Chinese characters are
left as is.
The problem appears on PostgreSQL 8.0.7 (on WinXP) where the upper()
result is apparently blank (this is via pgAdmin III). Worde still, via
JDBC I am getting:
java.sql.SQLException: 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.
Is this a bug or a change of behaviour between versions?
Is there some way I can get the 7.4.13 behaviour in 8.0.7?
TIA,
Scott
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
