From: Eugene E. <sad@bankir.ru>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: have you feel anything when you read this ?
Date: Tue, 21 Mar 2006 13:36:20 +0300
Message-ID: <441FD724.8050802@bankir.ru> (raw)
In-Reply-To: <1142871030.17883.1.camel@state.g2switchworks.com>
References: <002701c64be1$de30c220$1e21100a@ghwk02002147>
<441E629F.4050806@bankir.ru>
<1142871030.17883.1.camel@state.g2switchworks.com>
Scott Marlowe wrote:
> 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.
I was not sure about MySQL, thank you for your explaination.
This ensures me that even MySQL server handles NUL-bytes properly
regardless to client problems.
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: sad@bankir.ru, smarlowe@g2switchworks.com
Subject: Re: have you feel anything when you read this ?
In-Reply-To: <441FD724.8050802@bankir.ru>
* 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