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-15 16:46:42
Message-ID: C6D52112.C4062%scott_ribe@killerbytes.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> So its not possible thats our parser.

And

> Second:string:Not really: thats the orignal string, and its a string:

Look again. Where is the null character in the original string? Why does
your encoded string end with "\0"? In what character set is null a legal
character?

Your encoder is incorrect.

--
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-15 16:52:52 Re: invalid byte sequence for encoding
Previous Message Grzegorz Jaśkiewicz 2009-09-15 16:34:25 Re: altering domains, allowing null