[AccessD] An interesting "feature" in SQL Server

Stuart McLachlan stuart at lexacorp.com.pg
Thu May 21 17:21:04 CDT 2009


You mean  "Natural Key, Unbound Form, Null is a Value" guy. :-)


On 21 May 2009 at 14:53, David McAfee wrote:

> Oh come on John, it wasnt like he called you a "Natural Key, Bound Form"
> guy. Now those are fighting words! ;)
> 
> 
> 
> On Thu, May 21, 2009 at 2:32 PM, jwcolby <jwcolby at colbyconsulting.com>wrote:
> 
> > Oh boy, here we go again.
> >
> > John W. Colby
> > www.ColbyConsulting.com
> >
> >
> > Arthur Fuller wrote:
> > > That's a good approach, David. The rest of this thread really causes skin
> > > rash due to its misunderstanding of the purpose of NULL values. NULL is a
> > > valid value. I've said this before and I'm saying it again. Force a NULL
> > > value to anything else (which includes defaulting a column to some value)
> > is
> > > IMO a fundamental design error, indicative of one of two problems:
> > >
> > > 1. you don't understand the data domain
> > > 2. the domain itself is incoherent.
> > >
> > > My $.02.
> > > Arthur
> >
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com





More information about the AccessD mailing list