From: Ken Johanson <pg-user@kensystem.com>
To: Oliver Jowett <oliver@opencloud.com>
Cc: James Im <im-james@hotmail.com>
Cc: pgsql-jdbc@postgresql.org
Subject: Re: invalid byte sequence for encoding "UTF8": 0x00
Date: Wed, 21 Feb 2007 23:37:51 -0700
Message-ID: <45DD3A3F.5050609@kensystem.com> (raw)
In-Reply-To: <45DAE076.1060407@opencloud.com>
References: <BAY7-F17FFE0E324AB3B642C547E96890@phx.gbl>
<45DAE076.1060407@opencloud.com>
Oliver Jowett wrote:
> James Im wrote:
>
>> I've got another problem. I sometimes get the following SQLException
>> when doing an insert:
>>
>> ERROR: invalid byte sequence for encoding "UTF8": 0x00
>
> You're trying to insert a string which contains a '\0' character. The
> server can't handle strings containing embedded NULs, as it uses C-style
> string termination internally.
>
At least on other servers/drivers I believe nulls are supported (and
should be according to some spec) (The only special-meaning char is
single quote).
I'm wondering how the binary protocol works insofar as handling the NULL
byte; does it precede it with a backslash? I'm wondering if this would
be possible for the String conversion as well -- just for sake of
consistency with other DBs (and since some API inevitable expect users
to send binary data through a char-sequence interface)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: pg-user@kensystem.com, oliver@opencloud.com, im-james@hotmail.com, pgsql-jdbc@postgresql.org
Subject: Re: invalid byte sequence for encoding "UTF8": 0x00
In-Reply-To: <45DD3A3F.5050609@kensystem.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox