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 C97C69DCB9C for ; Mon, 20 Mar 2006 12:10:35 -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 08314-07 for ; Mon, 20 Mar 2006 12:10:33 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id 8C7C29DCBC9 for ; Mon, 20 Mar 2006 12:10:31 -0400 (AST) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Mon, 20 Mar 2006 16:10:30 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 20 Mar 2006 10:10:30 -0600 Subject: Re: have you feel anything when you read this ? From: Scott Marlowe To: "Eugene E." Cc: pgsql-sql@postgresql.org In-Reply-To: <441E629F.4050806@bankir.ru> References: <002701c64be1$de30c220$1e21100a@ghwk02002147> <441E629F.4050806@bankir.ru> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1142871030.17883.1.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 20 Mar 2006 10:10:30 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.147 required=5 tests=[AWL=0.146, UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.147 X-Spam-Level: X-Archive-Number: 200603/310 X-Sequence-Number: 24656 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.