Re: Extending my question. Was: The relational model and relational algebra - why did SQL become the industry standard?
Date: 3 Mar 2003 23:10:12 +0100
Message-ID: <3e63d2c4.0_at_news.ruca.ua.ac.be>
Lauri Pietarinen wrote:
>Jan Hidders wrote:
>>
>>Well, your specific example involves recognizing that duplicate
>>elimination is not necessary in the view. That was something that was
>>researched as (relatively) recently as 1994:
>>
>> http://www.informatik.uni-trier.de/~ley/db/conf/icde/PaulleyL94.html
>
>OK, point being that if SQL had not had duplicates from the start the
>motivation for such research would have been much stronger, and we would
>have got results sooner.
Could be, but note that this would then be because you made things *harder*
for the implementors and forced them to think about these issues.
>>So it could very well that for this particular problem you are right.
>Meaning that "you can do more optimisations with set's"?
Meaning that in this case you might be right that for this particular query
the bag-based approach makes optimization a bit harder. However, after
giving it a bit more thought I doubt that even this is true. The problem is
just as difficult in a set-only as in a bag-based approach. In both cases
you can optimize a join followed by a project that projects out a certain
table by using only the index for the "invisible" table.
>>>Date is trying to take the relational model to it's full potential and I
>>>would claim that the SQL-mode of thinking is hindering us from achieving
>>>this. And this (in my view) is ultimately Date's criticism of Hector
>>>Garcia-Molina, Jeffrey D. Ullman, and Jennifer Widom, DATABASE SYSTEM
>>>IMPLEMENTATION.
>>
>>Is he really criticizing this book? I don't get that impression from the
>>"double trouble" article on dbdebunk.
>
>No? At least he criticises some parts of it, or do you disagree?
Kind regards,
- Jan Hidders
