Path: news.cambrium.nl!textnews.cambrium.nl!feeder3.cambriumusenet.nl!feed.tweaknews.nl!193.201.147.78.MISMATCH!feeder.news-service.com!postnews.google.com!j25g2000yqa.googlegroups.com!not-for-mail
From: Cimode <cimode@hotmail.com>
Newsgroups: comp.databases.theory
Subject: Re: The Relational Model & Queries That Naturally Return Duplicate Rows
Date: Sat, 9 Oct 2010 15:14:29 -0700 (PDT)
Organization: http://groups.google.com
Lines: 64
Message-ID: <72885253-9078-4a7d-a7e6-256ca1af6357@j25g2000yqa.googlegroups.com>
References: <0d9300b0-88be-40f3-ae94-97d1beac56dd@j18g2000yqd.googlegroups.com>
 <03efca15-4020-4ea2-b0c3-cfb8723e713f@l20g2000yqm.googlegroups.com> <746c7840-b5cb-4a16-98ff-aa66c3def471@j25g2000yqa.googlegroups.com>
NNTP-Posting-Host: 82.230.226.33
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1286662471 8823 127.0.0.1 (9 Oct 2010 22:14:31 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 9 Oct 2010 22:14:31 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: j25g2000yqa.googlegroups.com; posting-host=82.230.226.33; posting-account=ICwiDwoAAADmc5U6HcJXmtqEzRkHXlWU
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6; fr-fr)
 AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9,gzip(gfe)
Xref:  news.cambrium.nl

On 9 oct, 13:19, Erwin <e.sm...@myonline.be> wrote:
> On 8 okt, 21:36, Cimode <cim...@hotmail.com> wrote:
>
>
>
>
>
> > On 8 oct, 15:44, Seun Osewa <seun.os...@gmail.com> wrote:
>
> > > Hi,
>
> > > It's commonly understood that in the relational model:
>
> > > =A0 =A01. Every relational operation should yield a relation.
> > > =A0 =A02. Relations, being sets, cannot contain duplicate rows.
>
> > > Imagine a 'USERS' relation that contains the following data.
>
> > > ID FIRST_NAME LAST_NAME
> > > =A01 Mark =A0 =A0 =A0 Stone
> > > =A02 Jane =A0 =A0 =A0 Stone
> > > =A03 Michael =A0 =A0Stone
>
> > > If someone runs the query "select LAST_NAME from USERS", a typical
> > > database will return:
>
> > > LAST_NAME
> > > Stone
> > > Stone
> > > Stone
>
> > > Since this is not a relation - because it contains duplicate rows -
> > > what should an ideal RDBMS return?
>
> > > Regards.
>
> > Rephrase your query in plain word english and you will find the answer
> > is obvious.
>
> > Suppose that appart from you, there are two members of your family,
> > bearing the same name than you working in your company. =A0Suppose you
> > ask your best friend, that talks to you on a daily basis, visiting
> > *Give me the LAST NAMES of ALL EMPLOYEES of my company* ? =A0What will
> > you think if that friend repeats three time the same thing.- Tekst uit =
oorspronkelijk bericht niet weergeven -
>
> > - Tekst uit oorspronkelijk bericht weergeven -
>
> Allthough your intent is obviously right, it might be helpful to
> actually spell out the answer, instead of answering the question with
> a counterquestion ... =A0Even if that counterquestion seems more than
> rhetorical enough _TO YOU_.
>
> The OP asked the very same question on another forum too. =A0I suppose
> he is trying to get "second opinion" or some such.
In this case, the answer is much less interesting than the reasoning
driving it.  Getting an unintuitive point across to somebody who
probably never read any significant RM theory material requires
different language and lexicology than the formal one.

At best, it triggers further interest on the subject, at worst, it
scares database practitioner wannabes who don't want to put some
effort onto understanding things.  The OP seems to belong to the
former (I hope).
