Forum OpenACS Q&A: Unicode Error on Postgres

Collapse
1: Unicode Error on Postgres
Posted by Malte Sussdorff on 02/08/04 05:09 PM
What did I miss when setting up postgres if I get an error like this in my error log (after uploading a file called "zusatzprüfung", mind the Umlaut):

=====

[08/Feb/2004:17:07:25][23572.163850][-sched:25-] Error: Ns_PgExec: result status: 7 message: ERROR:  invalid byte sequence for encoding "UNICODE": 0xc3

transaction error
[08/Feb/2004:17:07:25][23572.163850][-sched:25-] Error: Aborting transaction due to error:
Database operation "dml" failed (exception ERROR, "ERROR:  invalid byte sequence for encoding "UNICODE": 0xc3
")

ERROR:  invalid byte sequence for encoding "UNICODE": 0xc3

SQL:
                    insert into index2
                        (lexem,tid,pos)
                        values
                        ('zusatzprÃ',4521,
                        '{17}')

Collapse
2: Re: Unicode Error on Postgres (response to 1)
Posted by Joel Aufrecht on 02/08/04 06:22 PM
Two things to check - did you create the database -E UNICODE?  there's some simple psql command to check.  And, is the AOLserver running utf-8?  Dunno if the second one matters.
Collapse
3: Re: Unicode Error on Postgres (response to 2)
Posted by Andrei Popov on 02/08/04 10:01 PM
psql -l from command prompt will ist all databases and their encodings
Collapse
4: Re: Unicode Error on Postgres (response to 2)
Posted by Malte Sussdorff on 02/09/04 08:57 AM
The database runs in UNICODE and the AOLserver has the OuputCharset as well as URLCharset set to utf-8.

This is only a problem with the file-names of uploaded files. Everything else works fine, all content is stored correctly and switching to arabic as the locale works fine as well.

Collapse
5: Re: Unicode Error on Postgres (response to 4)
Posted by Andrei Popov on 02/09/04 11:32 AM
Maybe this is browser-related?  Can it be that form encoding is not correctly specified, resulting in translation?