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 f43NFIA44705 for ; Thu, 3 May 2001 19:15:18 -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 f43NEcR14600; Thu, 3 May 2001 19:14:38 -0400 (EDT) To: Stephen Davies cc: Sanjay Arora , 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: <200105032311.IAA07534@mustang.sdc.com.au> References: <200105032311.IAA07534@mustang.sdc.com.au> Comments: In-reply-to Stephen Davies message dated "Fri, 04 May 2001 08:41:13 +0930" Date: Thu, 03 May 2001 19:14:37 -0400 Message-ID: <14597.988931677@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200105/17 X-Sequence-Number: 1543 Stephen Davies writes: > I changed my DDL to make the unique (sequence-based) keys on the tables > involved "not null". This sees to have stopped the inserts but has not > caused any error messages. Are you looking for error messages in the postmaster log, or are you just believing what Microsoft software tells you? Running the postmaster with query logging enabled (-d2 postmaster switch) would be even more helpful, since then we could see what these mysterious queries are ... regards, tom lane