Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!ucbvax!mtxinu!sybase!jeffl@sybase.Sybase.COM
From: jeffl@sybase.Sybase.COM (Jeff Lichtman)
Newsgroups: comp.databases
Subject: Re: SQL Precompilers
Message-ID: <10388@sybase.sybase.com>
Date: 2 Aug 90 06:52:46 GMT
References: <1990Jul31.013321.5117@ingres.Ingres.COM>
Sender: news@Sybase.COM
Lines: 15

>>...or a plan to the database engine from a user program...
>>this is almost always a bad idea...
> I claim that anything *other* than submitting a pre-baked query plan for
> execution is almost always a bad idea...

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.
---
Jeff Lichtman at Sybase
{mtxinu,pacbell}!sybase!jeffl  -or- jeffl@sybase.com
"Saints should always be judged guilty until they are proved innocent..."