>> Is it safe (or even required?) to change sqliteInt.h to >> >> #ifndef SQLITE_OMIT_TRIGGER >> void sqlite3ExprCodeAndCache(Parse*, Expr*); >> #else >> # define sqlite3ExprCodeAndCache(A,B) >> #endif >> > >The suggested change will probably fail. You can find out >by running: > > make fulltest
I can do this (sidenote: many of the vtab tests fail). I use cygwin on Win32 and run: sh configure makek fulltest Question: Where do I introduce SQLITE_OMIT_TRIGGER? >A safer fix would be to remove the #ifndef SQLITE_OMIT_TRIGGER >from around the sqlite3ExprCodeAndCache function. Thanks, will do. >You should also file a bug report. Done. ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------