Received: from sss.pgh.pa.us (sss.pgh.pa.us [216.151.103.158])
	by postgresql.org (8.11.3/8.11.1) with ESMTP id f43Ja8A68204
	for <pgsql-interfaces@postgresql.org>;
	Thu, 3 May 2001 15:36:08 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f43Ja3R00425;
	Thu, 3 May 2001 15:36:03 -0400 (EDT)
To: Sanjay Arora <sk@pobx.com>
cc: pgsql-interfaces@postgresql.org, goga@tc-internet.com,
	arminder@tc-internet.com
Subject: Re: Null values where they should not be...HELP Please!! 
In-reply-to: <200105031450.UAA27923@tcs.com> 
References: <200105031450.UAA27923@tcs.com>
Comments: In-reply-to Sanjay Arora <sk@pobx.com>
	message dated "Tue, 03 Oct 2000 20:25:31 -0000"
Date: Thu, 03 May 2001 15:36:03 -0400
Message-ID: <422.988918563@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200105/15
X-Sequence-Number: 1541

Sanjay Arora <sk@pobx.com> writes:
> Assuming even that the application is trying to store null where it should
> not, PG should raise an error, instead of accepting the same.

Indeed.  No one has reported any such problem before, AFAIR.  Are you
sure the columns are marked NOT NULL?

			regards, tom lane