X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 057EE9DD54F for ; Tue, 21 Mar 2006 06:38:49 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 36781-04 for ; Tue, 21 Mar 2006 06:38:51 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from moon.antora.ru (moon.antora.ru [83.222.21.34]) by postgresql.org (Postfix) with ESMTP id 7FB4C9DD551 for ; Tue, 21 Mar 2006 06:38:47 -0400 (AST) Received: from [217.26.17.26] (helo=[10.0.0.72]) by moon.antora.ru with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FLeGH-000IWs-7z; Tue, 21 Mar 2006 13:38:49 +0300 Message-ID: <441FD724.8050802@bankir.ru> Date: Tue, 21 Mar 2006 13:36:20 +0300 From: "Eugene E." User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050517) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Marlowe CC: pgsql-sql@postgresql.org Subject: Re: have you feel anything when you read this ? References: <002701c64be1$de30c220$1e21100a@ghwk02002147> <441E629F.4050806@bankir.ru> <1142871030.17883.1.camel@state.g2switchworks.com> In-Reply-To: <1142871030.17883.1.camel@state.g2switchworks.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.12 required=5 tests=[AWL=0.120] X-Spam-Score: 0.12 X-Spam-Level: X-Archive-Number: 200603/325 X-Sequence-Number: 24671 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.