home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!jvnc.net!netnews.upenn.edu!saul.cis.upenn.edu!limsoon
- From: limsoon@saul.cis.upenn.edu (Limsoon Wong)
- Newsgroups: comp.databases
- Subject: Re: nested SQL select
- Message-ID: <87028@netnews.upenn.edu>
- Date: 26 Aug 92 01:37:03 GMT
- References: <1992Aug14.071343.1758@neptune.inf.ethz.ch> <l990h3INN7it@jethro.Corp.Sun.COM> <1992Aug25.161811.6054@neptune.inf.ethz.ch>
- Sender: news@netnews.upenn.edu
- Organization: University of Pennsylvania
- Lines: 17
- Nntp-Posting-Host: saul.cis.upenn.edu
-
- In article <1992Aug25.161811.6054@neptune.inf.ethz.ch> marti@nugget.inf.ethz.ch (Robert Marti) writes:
- >Editorial comment: This posting is more of an academic exercise
- >than of practical interest. All I am trying to show is that any
- >_pure_ relational algebra expression can be translated into a
- >single SQL SELECT-statement -- for what it's worth ...
- >
- [stuff deleted]
- >
- > project[...](R - S) ----> project[...](R) - project[...](S)
-
- This one is not correct under the usual set-based semantics,
- since after the omission of some columns, previous distinct
- rows in R can become identified.
-
- Limsoon Wong.
-
-
-