From: | Daniel Schuchardt <d(dot)schuchardt(at)prodat-sql(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | invalid byte sequence for encoding |
Date: | 2009-09-13 16:51:15 |
Message-ID: | h8j7tv$e9l$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hy, i have some trouble with the new postgresql 8.4.
we check out the compatibility between postgres 8.1 and 8.4
so we have the following error:
invalid byte sequence for encoding "WIN1252": 0x00
can anyone say me a work-around?
We have to change the escape chars that are inserted by our parser,
right? Is it is possible to simulate the postgresql-8.1 behavoir? (some
special encoding e.g.)
UPDATE belzeil_frei SET bz_zubez= '*', bz_zubez_rtf=
'{\\rtf1\\ansi\\deff0{\\fonttbl{\\f0\\fnil\\fcharset0
Arial;}}\r\n\\viewkind4\\uc1\\pard\\lang1031\\fs20 *\r\n\\par }\r\n\0'
WHERE dbrid=295116
Result : ERROR: invalid byte sequence for encoding "WIN1252": 0x00
In that example i try to insert a "*" with rtf-encoding.
i have the same problem with SQL_ASCII
Daniel.
--
Daniel Schuchardt
/Softwareentwicklung/
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2009-09-13 17:32:44 | Re: schema proxying virtual database |
Previous Message | Ludwig Kniprath | 2009-09-13 16:00:21 | Re: How to match sets? |