Re: In an RDBMS, what does "Data" mean?
From: mAsterdam <mAsterdam_at_vrijdag.org>
Date: Fri, 04 Jun 2004 01:27:07 +0200
Message-ID: <40bfb3c2$0$15440$e4fe514c_at_news.xs4all.nl>
[chop]
> Sorry, not refusal, but even I get sick of my broken record on 1NF --
> that's why things are chopped up unnecessarily, in order to put them into
> 1NF. So, in the example I gave, there is no reason, in my opinion, not to
> have a single line of the invoice be stored in a tuple, allowing the lists
> to be elements of the tuple, just as the single-valued attributes are.
Date: Fri, 04 Jun 2004 01:27:07 +0200
Message-ID: <40bfb3c2$0$15440$e4fe514c_at_news.xs4all.nl>
>>Bill H wrote: >>>mAsterdam wrote: >>>>Dawn M. Wolthuis wrote: >>>>>It think it is worth noting that is far more difficult to retrieve an >>>>>invoice the way it looked originally after chopping it up >>>> >>>>You chopped it up. Why?
[chop]
> Sorry, not refusal, but even I get sick of my broken record on 1NF --
> that's why things are chopped up unnecessarily, in order to put them into
> 1NF. So, in the example I gave, there is no reason, in my opinion, not to
> have a single line of the invoice be stored in a tuple, allowing the lists
> to be elements of the tuple, just as the single-valued attributes are.
So you don't need the to share the internal structure. Don't do that, then. Received on Fri Jun 04 2004 - 01:27:07 CEST