From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Eugene E. <sad@bankir.ru>
Cc: pgsql-sql@postgresql.org
Subject: Re: have you feel anything when you read this ?
Date: Mon, 20 Mar 2006 10:10:30 -0600
Message-ID: <1142871030.17883.1.camel@state.g2switchworks.com> (raw)
In-Reply-To: <441E629F.4050806@bankir.ru>
References: <002701c64be1$de30c220$1e21100a@ghwk02002147>
<441E629F.4050806@bankir.ru>
On Mon, 2006-03-20 at 02:06, Eugene E. wrote:
> http://dev.mysql.com/doc/refman/5.0/en/news-5-0-19.html
> --- cut ---
> mysql no longer terminates data value display when it encounters a NUL
> byte. Instead, it displays NUL bytes as spaces. (Bug #16859)
> --- cut ---
Everyone here realizes that this is a mysql CLIENT bug, not server side.
i.e. if you're writing an application and request that binary text
string, you'll get it with nuls in it, just like you put in.
Now, I'm not sure that turning nulls into spaces is the best way to
handle this in the client. In fact, I'm sure it's not. But this is not
a server bug, it's a client bug.
Just FYI.
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-sql@postgresql.org
Cc: smarlowe@g2switchworks.com, sad@bankir.ru
Subject: Re: have you feel anything when you read this ?
In-Reply-To: <1142871030.17883.1.camel@state.g2switchworks.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