Re: invalid byte sequence for encoding - Mailing list pgsql-general

From Daniel Schuchardt
Subject Re: invalid byte sequence for encoding
Date
Msg-id 4AAD7449.8030100@prodat-sql.de
Whole thread Raw
In response to Re: invalid byte sequence for encoding  (Thomas Kellerer <spam_eater@gmx.net>)
List pgsql-general
Hi Thomas,

thanks a lot we will check out that parameter. But if i understand it in
  the correct way that parameter will turn off all escape quoting.

I have to check out,

thanks a lot.

Thomas Kellerer schrieb:
> Daniel Schuchardt wrote on 13.09.2009 18:51:
>> 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
>
>
> Sounds to me as if you need to set standard_conforming_strings to true
> in the postgresql.conf
>
> http://www.postgresql.org/docs/8.4/static/runtime-config-compatible.html#GUC-STANDARD-CONFORMING-STRINGS
>
>
> Thomas
>
>


--
Daniel Schuchardt
/Softwareentwicklung/

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

pgsql-general by date:

Previous
From: Daniel Schuchardt
Date:
Subject: Re: invalid byte sequence for encoding
Next
From: Marc Munro
Date:
Subject: Re: postgresql.key secure storage