X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 426B9D1B8BE; Thu, 11 Dec 2003 14:54:04 +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 49054-04; Thu, 11 Dec 2003 10:53:36 -0400 (AST) Received: from asmodeus.mcnaught.org (sp-260-1.net4.netcentrix.net [4.21.254.118]) by svr1.postgresql.org (Postfix) with ESMTP id 5E213D1BB6C; Thu, 11 Dec 2003 10:53:12 -0400 (AST) Received: from doug by asmodeus.mcnaught.org with local (Exim 3.36 #1) id 1AUSAz-0004md-00; Thu, 11 Dec 2003 09:52:25 -0500 To: "Nagib Abi Fadel" Cc: "generalpost" , "developPost" Subject: Re: Should we consider empty fields as NULL values when References: <001401c3bff4$49abd7f0$f664a8c0@nagib> From: Doug McNaught Date: Thu, 11 Dec 2003 09:52:25 -0500 In-Reply-To: <001401c3bff4$49abd7f0$f664a8c0@nagib> (Nagib Abi Fadel's message of "Thu, 11 Dec 2003 16:36:56 +0200") Message-ID: <87he07qudy.fsf@asmodeus.mcnaught.org> User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/20.7 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/628 X-Sequence-Number: 54022 "Nagib Abi Fadel" writes: > The issue is that since the column col1 is defined as character with > not null attribute, > > shouldn't we deny such inserts (i mean inserting empty fields)??? NULL and the empty string '' are *completely* different things. If you want to disallow empty strings as well as NULL, use a CHECK constraint on that column. -Doug