X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id EA32DD1B56E for ; Tue, 28 Oct 2003 15:42:14 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 12465-07 for ; Tue, 28 Oct 2003 11:41:47 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id A7D85D1B529 for ; Tue, 28 Oct 2003 11:41:42 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id h9SFfYit022446; Tue, 28 Oct 2003 10:41:34 -0500 (EST) To: sad Cc: "psql" Subject: Re: bug in working with TEXT constants ? In-reply-to: <200310281153.54160.sad@bankir.ru> References: <200310281153.54160.sad@bankir.ru> Comments: In-reply-to sad message dated "Tue, 28 Oct 2003 11:53:54 +0000" Date: Tue, 28 Oct 2003 10:41:34 -0500 Message-ID: <22445.1067355694@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/366 X-Sequence-Number: 15766 sad writes: > Then I expect natural possibility to store texts having zero characters. You expect wrong; we don't support embedded nulls in text values, nor in literal strings. You can store nulls in BYTEA fields, but you have to use bytea's escaping conventions to represent the value in SQL commands, eg, 'foo\\000bar'. regards, tom lane