invalid byte sequence for encoding - Mailing list pgsql-general

From Daniel Schuchardt
Subject invalid byte sequence for encoding
Date
Msg-id h8j7tv$e9l$1@news.hub.org
Whole thread Raw
Responses Re: invalid byte sequence for encoding  (Peter Eisentraut <peter_e@gmx.net>)
Re: invalid byte sequence for encoding  (Scott Ribe <scott_ribe@killerbytes.com>)
Re: invalid byte sequence for encoding  (Thomas Kellerer <spam_eater@gmx.net>)
List 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/

www.prodat-sql.de <http://www.prodat-sql.de>

pgsql-general by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: Re: schema proxying virtual database
Next
From: John R Pierce
Date:
Subject: Re: postgresql.key secure storage