Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!swrinde!ucsd!ames!amdahl!rtech!ingres!llama!jas
From: jas@llama.Ingres.COM (Jim Shankland)
Newsgroups: comp.databases
Subject: Re: SQL Precompilers
Message-ID: <1990Aug3.005023.9292@ingres.Ingres.COM>
Date: 3 Aug 90 00:50:23 GMT
References: <1990Jul31.013321.5117@ingres.Ingres.COM> <10388@sybase.sybase.com>
Reply-To: jas@llama.Ingres.COM (Jim Shankland)
Organization: The Eddie Group
Lines: 14

In article <10388@sybase.sybase.com> jeffl@sybase.Sybase.COM (Jeff Lichtman) writes:
>Precompiled queries are good.  I believe (please correct me if I'm wrong)
>that the original posting was talking about user-written query plans
>hard-coded into applications and sent to the server.  The problem here
>is that the compilation and plan storage are being done in the wrong
>place.  It's much better for the DBMS to compile and keep the plan,
>so all the user has to do is invoke it by name.

Yes; I agree entirely.  My apologies if I misunderstood.  Perhaps it's
just as well that we made this explicit, though, since someone else
asked why it wasn't good enough to feed SQL to the DBMS engine
on every query execution.

jas