Group, Compiling with -DSQLITE_DEBUG=1 has performance impacts as it adds other debug capability that we may not need. I noticed that there is also a define called SQLITE_OMIT_EXPLAIN in the source code. Is it possible to just set that define properly (I assume to undefine it or perhaps set it to 0) to enable the EXPLAIN capability without the overhead of the -DSQLITE_DEBUG=1 method?
Anyone know what the proper setting for SQLITE_OMIT_EXPLAIN should be on the commend line? Anyone tried this? thanks in advance, Mike Lowder GDAIS Virginia Beach, VA -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, September 29, 2006 2:31 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Problem with EXPLAIN in Sqlite-3.3.5 "Lowder, Brady M." <[EMAIL PROTECTED]> wrote: > Group, > > > Using sqlite-3.3.5 along with Tcl8.4.11 and Tk8.4.11, the EXPLAIN > command doesn't produce the desired result. EXPLAIN is used for > interpreting SELECT, INSERT, DELETE, UPDATE SQL commands. It appears > to be retrieving insufficent opcodes and erroneous data that don't > return a result from the SQL call. Performing the same with sqlite > 2.8.13 produces the desired results. Does anyone know what is causing this? > > EXPLAIN is omitted by default. Recompile with -DSQLITE_DEBUG=1 to turn it on. -- D. Richard Hipp <[EMAIL PROTECTED]> ------------------------------------------------------------------------ ----- To unsubscribe, send email to [EMAIL PROTECTED] ------------------------------------------------------------------------ ----- ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
