Re: Null and Void() - Or, Abandon All Hope Ye Who allow

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
Cc: Scott Ribe <scott_ribe(at)killerbytes(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Null and Void() - Or, Abandon All Hope Ye Who allow
Date: 2006-07-05 18:32:14
Message-ID: 877j2rq4wh.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Scott Marlowe <smarlowe(at)g2switchworks(dot)com> writes:

> However, there are often nulls that fall in the category of "who
> cares?" For those, null is a perfectly acceptable alternative, and
> there's no need for all the extra work.

There is often a need for special case values. Situations like "subscription
expiration date" for a subscription that shouldn't expire at all, or even
"income level" for users who refuse to give that information. Also for things
like the various NaN values.

I kind of wish SQL allowed for an arbitrary set of "special values" regardless
of data type rather than allow a single special value and have so many hard
coded magical behaviours.

--
greg

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Chris Browne 2006-07-05 18:36:35 Re: Notes on converting from MySQL 5.0.x to PostgreSQL
Previous Message Scott Marlowe 2006-07-05 18:08:06 Re: Null and Void() - Or, Abandon All Hope Ye Who allow