Re: invalid byte sequence for encoding

From: Scott Ribe <scott_ribe(at)killerbytes(dot)com>
To: Daniel Schuchardt <d(dot)schuchardt(at)prodat-sql(dot)de>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: invalid byte sequence for encoding
Date: 2009-09-13 19:48:24
Message-ID: C6D2A8A8.C3D40%scott_ribe@killerbytes.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> In that example i try to insert a "*" with rtf-encoding.

It's not the "*" causing the error, it's the "\0"--which I'm pretty sure is
not a valid character for an RTF file either. Do you have an encoder which
is just blindly reading through the null terminator of a C string and
including it in the encoded string.

--
Scott Ribe
scott_ribe(at)killerbytes(dot)com
http://www.killerbytes.com/
(303) 722-0567 voice

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Daniel Schuchardt 2009-09-13 20:21:09 Re: invalid byte sequence for encoding
Previous Message Peter Eisentraut 2009-09-13 19:40:41 Re: invalid byte sequence for encoding