Re: invalid multibyte character for locale

I ended up using SQL_ASCHII and could see lower works fine but on extended
chars it does nothing.
SO if that's what your shooting for it worked ok for me.
I would have preferred to have my encoding Unicode , but don't want to
figure out why the odbc driver was not able to insert extended chars.

I could insert the extended chars fine in pgadmin and also with .net driver
with a encoding = Unicode, but we have lots of asp that will use the odbc
driver so I had to go with SQL_ASCHII to avoid getting errors.

Joel Fradkin

Wazagua, Inc.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel. 941-753-7111 ext 305

jfradkin(at)wazagua(dot)com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
C 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc
This email message is for the use of the intended recipient(s) and may
contain confidential and privileged information. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and delete and destroy
all copies of the original message, including attachments.

-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
Sent: Thursday, February 24, 2005 10:16 AM
To: Bjoern Metzdorf
Cc: Pgsql-Admin (E-mail)
Subject: Re: [ADMIN] invalid multibyte character for locale

Bjoern Metzdorf <bm(at)turtle-entertainment(dot)de> writes:
> Is 8.0 just stricter or is this just a side effect
> of your fix for multibyte upper/lower problem for locale != C?

Both those statements are true.

> If 7.3 and 7.4 behaviour is intended, is there a way to let 8.0 behave
> the same?

I don't know what behavior you thought you were getting from upper/lower
on UTF-8 data in 7.4, but it was surely not correct. If you want to
duplicate that misbehavior, try SQL_ASCII with C locale. This does not
stop you from storing UTF-8 in your database, mind you --- it just
loses validation of encoding sequences and conversion to other schemes.

But having said that, upper() should work if the locale matches the
encoding. You might take the trouble to trace down exactly what data
value it's barfing on.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend