Re: when to use NULL and when to NOT NULL DEFAULT '' - Mailing list pgsql-general

From Michael Glaesemann
Subject Re: when to use NULL and when to NOT NULL DEFAULT ''
Date
Msg-id 975499A0-192E-11D9-A09B-000A95C88220@myrealbox.com
Whole thread Raw
In response to Re: when to use NULL and when to NOT NULL DEFAULT ''  (David Garamond <lists@zara.6.isreserved.com>)
Responses Re: when to use NULL and when to NOT NULL DEFAULT ''  (David Garamond <lists@zara.6.isreserved.com>)
List pgsql-general
On Oct 8, 2004, at 10:19 PM, David Garamond wrote:

> Michael Glaesemann wrote:
>> In any case, one would never use NULL. Either the domain includes a
>> value for all possible values (including N/A) or you set up the db
>> schema appropriately.
>
> Hm, that can be painful. What if I have ten optional attributes;
> separate them to ten different tables?

Strictly? That's how I understand it. Whether or not it's performant
under PostgreSQLis another matter. :)

Michael Glaesemann
grzm myrealbox com


pgsql-general by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: text + text
Next
From: Tom Lane
Date:
Subject: Re: Question about timezones