Path: news.easynews.com!easynews!feed.news.qwest.net!news.uswest.net.POSTED!not-for-mail
From: "Daniel Guntermann" <guntermann@uswest.net>
Newsgroups: comp.databases.theory
References: <60360d48.0112291928.2e7c5818@posting.google.com> <4fdv2ugs6u4m8et1pr5bb7sbsmrsmdu350@4ax.com> <1uZX7.6$Nq6.437@petpeeve.ziplink.net> <s4313usa6t9oof1m0tv36tqusv7sq2qiqv@4ax.com> <XH0Y7.9$Nq6.589@petpeeve.ziplink.net>
Subject: Re: UNIQUE and NULL in SQL
Lines: 42
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2615.200
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Message-ID: <1J6Y7.974$S61.151977@news.uswest.net>
Date: Mon, 31 Dec 2001 15:33:12 -0800
NNTP-Posting-Host: 65.102.155.40
X-Trace: news.uswest.net 1009842109 65.102.155.40 (Mon, 31 Dec 2001 17:41:49 CST)
NNTP-Posting-Date: Mon, 31 Dec 2001 17:41:49 CST
Xref: easynews comp.databases.theory:19377
X-Received-Date: Mon, 31 Dec 2001 21:16:26 MST (news.easynews.com)


David Cressey <david@dcressey.com> wrote in message
news:XH0Y7.9$Nq6.589@petpeeve.ziplink.net...

> Where I would take issue with you is when you call "Not Applicable"  a
> "value".  It isn't a value, IMHO.  It's a conclusion drawn from the fact
> that a value is not present at a given intersection of a row and a column.

Maybe in some cases.  But other 'values' that could also be valid in place
of a value not present at a given intersection of a row and a column (what
is currently implemented by many designers) could also include 'Not Known',
'Not Given', 'Not Confirmed', 'Irrevalent', etc.  Any one of these
classifications, in my opinion, are values if they are considered part of
the domain of any particular attribute as defined by the data administrator
or user.  They are values in my opinion because they represent true facts,
and are therefore reflected in a manner consistent with something like:  The
person identified by NAME 'Jan' is of a gender type that is 'NOT KNOWN'.  A
case can be made for all the various variations that are often confused with
the NULL.

Why are they facts?  Because they meet the constraints of a domain defined
for a relation attribute and they are true predicates as reflected in the
body of a relation variable.


> And I would maintain that NULL is never a value, regardless of the
> conclusion drawn  from it.  And I would further maintain that this is not
a
> matter of opinion, but a matter of definition.

I'll agree.
>
> --
> Regards,
>     David Cressey
>     www.dcressey.com
> "Mark Preston" <mark@mpreston.demon.co.uk> wrote in message
> news:s4313usa6t9oof1m0tv36tqusv7sq2qiqv@4ax.com...
>
>


