NULL value vs. DEFAULT value. - Mailing list pgsql-general

From James B. Byrne
Subject NULL value vs. DEFAULT value.
Date
Msg-id 52753.216.185.71.25.1299596075.squirrel@webmail.harte-lyne.ca
Whole thread Raw
Responses Re: NULL value vs. DEFAULT value.  (Scott Ribe <scott_ribe@elevated-dev.com>)
Re: NULL value vs. DEFAULT value.  (Thom Brown <thom@linux.com>)
Re: NULL value vs. DEFAULT value.  (Raymond O'Donnell <rod@iol.ie>)
Re: NULL value vs. DEFAULT value.  ("David Johnston" <polobo@yahoo.com>)
List pgsql-general
version = postgresql-8.4.4-2PGDG.el5.src.rpm

I am seeing this problem and I cannot explain why it is happening.
Evidently I misapprehend something about the interaction of NOT NULL
and DEFAULT.  If someone could tell me what the actual case is I
would appreciate it very much.

The table definition looks like this:
CREATE TABLE ca_customs_shipments (
    id integer NOT NULL,
.  .  .
    weight_mass_gross numeric(14,4) DEFAULT 0.0 NOT NULL,
    weight_mass_gross_uom character varying(3)
      DEFAULT '   '::character varying NOT NULL,
    weight_mass_net numeric(14,4) DEFAULT 0 NOT NULL,
    weight_mass_net_uom character varying(3)
      DEFAULT '   '::character varying NOT NULL,
.  .  .
);


My question is:  Why am I getting a NULL exception?  Should I only
specify DEFAULT and drop the NOT NULL constraint?


--
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB@Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3


pgsql-general by date:

Previous
From: "Francisco Figueiredo Jr."
Date:
Subject: Re: unexpected EOF on client connection vs 9.0.3
Next
From: Scott Ribe
Date:
Subject: Re: NULL value vs. DEFAULT value.