Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!metaphor!xymox!philf
From: philf@xymox.metaphor.com (Phil Fernandez)
Newsgroups: comp.databases
Subject: Re: Parsing Query Languages in the Client or Server
Message-ID: <800@metaphor.Metaphor.COM>
Date: 25 Sep 89 01:17:02 GMT
References: <6155@sybase.sybase.com> <631@daitc.daitc.mil>
Sender: news@metaphor.Metaphor.COM
Reply-To: philf@xymox.metaphor.com (Phil Fernandez)
Organization: Metaphor Computer Systems, Mountain View, CA
Lines: 33

In article <631@daitc.daitc.mil> jkrueger@daitc.daitc.mil (Jon Krueger) writes:
>forrest@sybase.com writes:
>...
>>Detecting syntax errors in the client can prevent sending a
>>syntactically incorrect query over a potentially slow network.
>>It would take fewer resources to find out that a query is syntactically
>>incorrect.
>
>Fewer bottlenecked resources, perhaps.  But isn't that what the
>validations, parsing, and generation logic in the front end tool
>is for?  In other words, isn't this a solved problem, at least
>for well behaved applications?
>...

Exactly.  Definitely a solved problem.  At Metaphor, our whole
business depends on building sophisticated (but easy-to-use) graphical
interfaces to relational data bases.  All of our various query
applications generate SQL, but no end-user ever sees SQL.  And, none
of our query applications generate malformed SQL, so no real need for
SQL syntax-checking on the client.

pmf

(These opinions are mine only; Metaphor pays me for real opinions)



+-----------------------------+----------------------------------------------+
| Phil Fernandez              |             philf@metaphor.com               |
|                             |     ...!{apple|decwrl}!metaphor!philf        |
| Metaphor Computer Systems   |"Does the body rule the mind, or does the mind|
| Mountain View, CA           | rule the body?  I dunno..." - Morrissey      |
+-----------------------------+----------------------------------------------+