Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!cimshop!davidm From: cimshop!davidm@uunet.UU.NET (David S. Masterson) Newsgroups: comp.databases Subject: Re: SQL Precompilers - Revisited Message-ID: Date: 10 Aug 90 03:07:51 GMT References: <1990Aug8.153529.12164@dg-rtp.dg.com> <26852@pasteur.Berkeley.EDU> Sender: davidm@cimshop.UUCP Followup-To: comp.databases Distribution: comp Organization: Consilium Inc., Mountain View, California. Lines: 19 In-reply-to: mao@eden's message of 8 Aug 90 18:04:30 GMT In article <26852@pasteur.Berkeley.EDU> mao@eden (Mike Olson) writes: i agree that precompilation makes canned apps run faster, and that the speed win is critical in high-throughput environments, like airline reservations. but the database engine has to understand what changes invalidate the compiled plan, and has to do the right thing. this is a lot harder than it looks. to do it right, you need perfect information on database state. perfect information is very expensive. I just wanted to point out something with respect to this thread. You said "precompilation makes canned apps run faster" which is something altogether different than "embedded SQL makes canned apps run faster". The two have nothing to do with one another, agreed? -- ==================================================================== David Masterson Consilium, Inc. uunet!cimshop!davidm Mtn. View, CA 94043 ==================================================================== "If someone thinks they know what I said, then I didn't say it!"