home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases
- Path: sparky!uunet!stanford.edu!ames!nsisrv!stars.gsfc.nasa.gov!thompson
- From: thompson@stars.gsfc.nasa.gov (William Thompson, code 682.1, x2040)
- Subject: Re: nested SQL select
- Message-ID: <12AUG199213085712@stars.gsfc.nasa.gov>
- News-Software: VAX/VMS VNEWS 1.4-b1
- Sender: usenet@nsisrv.gsfc.nasa.gov (Usenet)
- Nntp-Posting-Host: stars.gsfc.nasa.gov
- Organization: NASA/GSFC-Laboratory for Astronomy and Solar Physics
- References: <3761@keele.keele.ac.uk> <l8h5i5INNhvg@jethro.Corp.Sun.COM>
- Date: Wed, 12 Aug 1992 17:08:00 GMT
- Lines: 18
-
- In article <l8h5i5INNhvg@jethro.Corp.Sun.COM>, jdr@starflight.Corp.Sun.COM
- writes...
- >In article 3761@keele.keele.ac.uk, csa09@seq1.keele.ac.uk (Paul Singleton)
- writes:
- >>Is there a general algorithm for translating relational algebra expressions
- >>into SQL? Or a preprocessor from sensible SQL to real-world SQL? Or have
- >>I (and my colleagues) missed something obvious?
- >
- >You've missed our thread on "SQL Shortcomings", in which we have shown why
- >SQL is brain-damaged and needs to be stamped out.
-
- Not to start any flame wars, but is anything else but SQL being worked on as a
- standard for intercommunication between different vendors databases? We're
- going to be using SQL because we have that requirement. I haven't heard of any
- non-vendor-specific developments of relational languages other than SQL, but
- would be interested to hear if there are.
-
- Bill Thompson
-