Re: RFC: A brief guide to nulls

From: Ludwig Lim <lud_nowhere_man(at)yahoo(dot)com>
To: dev(at)archonet(dot)com
Cc: PostgreSQL Mailing List <pgsql-sql(at)postgresql(dot)org>
Subject: Re: RFC: A brief guide to nulls
Date: 2003-01-16 01:59:32
Message-ID: 20030116015932.10944.qmail@web80304.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql


--- dev(at)archonet(dot)com wrote:
> There have been a few posts recently where people
> have had problems with
> nulls. Anyone got comments on the below before I
> submit it to techdocs?
>
> TIA
>
> - Richard Huxton
>
> A Brief Guide to NULLs
> ======================
>
> What is a null?
> ===============
> A null is *not* an empty string.
> A null is *not* a value.
> A null is *not* a "special" value.
> A null is the absence of a value.
>
>
> What do nulls mean?
> ===================
> Well, they *should* mean one of two things:
> 1. There is no applicable value
> 2. There is a value but it is unknown

Good job!, it sure helps people who don't much
background on formal database theory.

What about adding this to the section "What does
nulls mean"
--> 3) No value has yet been assigned to that
particular attribute (field).


I think it would also be nice if you can add a
section on functions that deals with NULL such as
nullif() and coalesce(). These functions help users
interpret NULL values.

best regards,

ludwig

__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Stephan Szabo 2003-01-16 02:02:12 Re: joining from multiple tables
Previous Message Joseph Shraibman 2003-01-16 01:43:29 joining from multiple tables