Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> comp.databases.theory -> Re: Extending my question. Was: The relational model and relational algebra - why did SQL become the industry standard?

Re: Extending my question. Was: The relational model and relational algebra - why did SQL become the industry standard?

From: Bob Badour <bbadour_at_golden.net>
Date: Sun, 9 Mar 2003 17:41:21 -0500
Message-ID: <_SPaa.419$fY2.63258760@mantis.golden.net>


"Jan Hidders" <jan.hidders_at_REMOVE.THIS.ua.ac.be> wrote in message news: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.

Are you saying that in a choice between "harder requiring more careful thought from dbms implementors" and "harder requiring more careful thought from dbms end-users", you would opt to burden the end-users? I think that burdening the dbms implementors will necessarily improve quality and that burdening end-users will necessarily degrade quality. Received on Sun Mar 09 2003 - 16:41:21 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US