Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28]) by postgresql.org (8.11.3/8.11.1) with SMTP id f43GixA07393 for ; Thu, 3 May 2001 12:44:59 -0400 (EDT) (envelope-from pgsql-interfaces-owner@postgresql.org) Received: from tcs.com ([202.9.155.119]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f43EvuA74628 for ; Thu, 3 May 2001 10:58:00 -0400 (EDT) (envelope-from sk@pobx.com) Received: from tcispl-ntws4 ([192.168.1.21]) by tcs.com (8.9.3/8.9.3) with SMTP id UAA27923; Thu, 3 May 2001 20:20:55 +0530 Message-Id: <200105031450.UAA27923@tcs.com> X-Sender: sanjay@tcs.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 03 Oct 2000 20:25:31 +0000 To: pgsql-interfaces@postgresql.org From: Sanjay Arora Subject: Null values where they should not be...HELP Please!! Cc: goga@tc-internet.com, arminder@tc-internet.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Archive-Number: 200105/12 X-Sequence-Number: 1536 I am using postgreSQL v. 7.0.2 on RH Linux 6.2 on the server with VB6 Application accessing the DB through postgrSQL ODBC driver v. 6.50. We have been running one application for a few months now and everything seemed to be fine and dandy. We are now exploring PG 7.1 and in the process of dumping the data for upload to 7.1 for testing, we found something very strange. - One Table has its default value as false, and has a constraint that it can't b null, still there are a lot of values that are NULL. - A serial field supposed to be "not null" also has a lot of nulls. - boolean fields with default values specified have nulls. Assuming even that the application is trying to store null where it should not, PG should raise an error, instead of accepting the same. Anyone encountered this before? Where should I look for a fix to this particular problem while we are testing PG 7.1 My thanks in Advance