Re: [sqlite] Unrevolved _sqlite3ExprCodeAndCache with SQLITE_OMIT_TRIGGER

2006-08-25 Thread Ralf Junker
>> 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: > >

Re: [sqlite] Unrevolved _sqlite3ExprCodeAndCache with SQLITE_OMIT_TRIGGER

2006-08-25 Thread drh
Ralf Junker <[EMAIL PROTECTED]> wrote: > Lattest cvs sqlite version: > > If SQLITE_OMIT_TRIGGER is set, linker complains about an unresolved > _sqlite3ExprCodeAndCache symbol. > > sqlite3ExprCodeAndCache is defined in expr.c and wrapped with #ifndef > SQLITE_OMIT_TRIGGER. > > However, referenc

[sqlite] Unrevolved _sqlite3ExprCodeAndCache with SQLITE_OMIT_TRIGGER

2006-08-25 Thread Ralf Junker
Lattest cvs sqlite version: If SQLITE_OMIT_TRIGGER is set, linker complains about an unresolved _sqlite3ExprCodeAndCache symbol. sqlite3ExprCodeAndCache is defined in expr.c and wrapped with #ifndef SQLITE_OMIT_TRIGGER. However, references in insert.c, line 536 update.c, line 348 and 362