Re: Extending my question. Was: The relational model and relational algebra - why did SQL become the industry standard?
Date: Tue, 18 Feb 2003 18:30:03 -0500
Message-ID: <b2ufiq$g10$1_at_slb9.atl.mindspring.net>
Excellent question. Before the present discussion, I would have
said that the logical model of multisets is conceptually close to
some real-world models, and certainly a good logical model for
the "relaxed" relational model implemented by many "R"DBMS
products, where the distinguishing attribute of rows is hidden.
That said, there's also room for confusion about whether one
conceptualizes the logical model as representing bags that
can contain indistinguishable duplicates (imagine the bag is
constantly being shaken, so we can't even say "the John Smith
at the bottom of the bag"), or as representing an inventory of
distinct entities with the additional attribute of multiplicity.
These two conceptualizations of the logical model lead naturally
to two distinct physical implementations. The more natural one
(in my mind) of "bags" is the more problematic, because no
computer I've ever used has a 30 Gig "hard bag"--there will
necessarily be an additional attribute, hidden or not, that internally
distinguishes every item. The less natural one, using multiplicities,
is not as convenient for some operations, such as displaying the
contents of a multiset (with no apologies for the fact that an order
attribute is acceptable with regard to a result set, because the
display and the bag are two different things), but using multiplicities
does a better job of representing the logical model, given the
reality of actual physical computers.
SK
Bob Badour wrote:
>If the facts are truly indistinguishable, they are a single fact and we have
>a model based on sets. If they only represent multiplicities, one really has
>a relational logical data model with an implicit count attribute.
>
>What benefit does this implicit attribute provide?
>
>
>
>>SK
>>
>>
>>
>>>
>>>
>
>
>
>
Received on Wed Feb 19 2003 - 00:30:03 CET