Re: On specialization constraints time of application
Date: Sun, 14 Jun 2009 13:58:48 -0400
Message-ID: <tTaZl.13253$im1.6859_at_nlpi061.nbdc.sbc.com>
"Cimode" <cimode_at_hotmail.com> wrote in message
news:bf51c5b8-57fd-4395-a3ed-987e5843fbb4_at_f19g2000yqo.googlegroups.com...
<snip>
> > > Because they ignore RM definitions about, SQL developpers also ignore
My experience is different, but I also don't want this to turn into a
pissing contest.
Received on Sun Jun 14 2009 - 19:58:48 CEST
> > > that drawbacks of using nulls far outweights any advantages.
> >
> > I would have used 'misusing nulls' instead of 'using nulls' because
> > judicious use of nulls can actually reduce both development and
> > execution
> > time, as well as maintenance, especially if decomposition would
> > introduce
> > complicated interrelational constraints. For example, a schema for
> > married
> > employees,
> >
> > MarriedEmployees {EMP#, NameOfSpouse}
> >
> > where NameOfSpouse can be null is a lot easier to maintian than a pair
> > of
> > schemata,
> I do not want ot make this an offtopic debate about whether NULLS are
> a good thing or not. I can only say that it is not my experience.