Path: utzoo!attcan!uunet!dgis!daitc!jkrueger
From: jkrueger@daitc.daitc.mil (Jon Krueger)
Newsgroups: comp.databases
Subject: Re: Parsing Query Languages in the Client or Server
Message-ID: <641@daitc.daitc.mil>
Date: 27 Sep 89 14:07:48 GMT
References: <6155@sybase.sybase.com> <17450@pasteur.Berkeley.EDU> <632@daitc.daitc.mil> <6253@sybase.sybase.com> <637@daitc.daitc.mil> <6291@sybase.sybase.com>
Organization: DTIC Special Projects Office (DTIC-SPO), Alexandria VA
Lines: 26

OK, I'll provide an example.  The database is movies, the schema are
	film(fname,fdate,director,company,country,language)
	actor(aname,bdate,sex,height)
	cast(fname,aname,role,charname)

This will allow us to put all sorts of delightful queries.  For instance,
has the average height of leading men decreased over the last twenty
years?  What actors have directed their own movies?  But the users of
this database are more likely to want to know: what films has Fred
Astaire played in?  In which of them did he appear with Ginger Rogers?
And so on.

>Let's agree on the scenario.  For server checking, a batch of SQL
>(procedure definition or ad-hoc) is sent straight to the server.  
>Each batch must be validated on its own, independent of previously-run
>batches.  

OK.  By "batch" I assume you mean a "bunch"; that is, you intend to
support interactive applications?  Please supply some sample queris.
Then we'll run through the whole scenario.  

-- Jon
-- 
Jonathan Krueger    jkrueger@daitc.daitc.mil   uunet!dgis!jkrueger
Isn't it interesting that the first thing you do with your
color bitmapped window system on a network is emulate an ASR33?