Path: csiph.com!x330-a1.tempe.blueboxinc.net!aioe.org!news.glorb.com!newsfeeds.ihug.co.nz!lust.ihug.co.nz!ihug.co.nz!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.lang.java.programmer Subject: Re: SQL Puzzle - too many dimensions Followup-To: comp.lang.java.programmer Date: Tue, 10 May 2011 13:50:14 +1200 Organization: Geek Central Lines: 9 Message-ID: References: <3Boxp.9547$HF3.5013@newsfe03.iad> <92r02mF24dU1@mid.individual.net> NNTP-Posting-Host: 118-92-95-178.dsl.dyn.ihug.co.nz Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit X-Trace: lust.ihug.co.nz 1304992214 14819 118.92.95.178 (10 May 2011 01:50:14 GMT) X-Complaints-To: abuse@ihug.co.nz NNTP-Posting-Date: Tue, 10 May 2011 01:50:14 +0000 (UTC) User-Agent: KNode/4.4.7 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3889 In message <92r02mF24dU1@mid.individual.net>, Robert Klemme wrote: > That's called an "inline view". The only reason there’s a special term for it is because SQL doesn’t treat tables/views as first-class objects. This is an example of a situation where a little bit more orthogonality could have made the language much simpler.