Path: utzoo!attcan!utgpu!watmath!att!tut.cis.ohio-state.edu!mailrus!cs.utexas.edu!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: <632@daitc.daitc.mil>
Date: 21 Sep 89 21:02:46 GMT
References: <6155@sybase.sybase.com> <17450@pasteur.Berkeley.EDU>
Organization: DTIC Special Projects Office (DTIC-SPO), Alexandria VA
Lines: 17

jas@postgres.uucp (James Shankland) writes:

>In article <6155@sybase.sybase.com> forrest@sybase.com writes:
>("Parsing" here means just the context-free stuff; the semantic checking
>pretty much has to be done in the server, which has the system catalogs.)

One of the nice things about keeping the data dictionary in ordinary
tables is that the application can use them to perform the same checks.
This can help distribute the load by trapping bad queries before they're
sent to the server.  But the server still has to check anyway for all
the queries that are sent it.

-- 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?