petern wrote:
> Regarding sqlite3_trace_v2(db, SQLITE_TRACE_PROFILE,...). Calls to
> sqlite3_sql() on the third trace callback parameter (cast to sqlite_stmt*)
> do retrieve the correct part of the the original sqlite3_exec input SQL
> string except for ill formed SQL. Apparently the
Hi Clemens.
Found the problem. My IDE is picking up other installed libsqlite3.so. It
was wrong to think that uninstalling the distro's SQLite package would
purge it from /usr/lib. Other copies still exist. I'm sure glad the
project is now linking the correct library file!
Regarding
petern wrote:
> linker says -> "undefined reference to `sqlite3_trace_v2'"
Then your distribution's package appears to be compiled with
SQLITE_OMIT_TRACE.
Just add sqlite3.c to your project.
Regards,
Clemens
___
sqlite-users mailing list
Clemens. I'm trying you suggestion but...
linker says -> "undefined reference to `sqlite3_trace_v2'"
[I am linking to libsqlite3.so. Version by sqlite_version() is 3.19.3.]
Is sqlite3_trace_v2() defined by a SQLite compile time option and if so
what is it?
Help page has only negative
petern wrote:
> Is there a C API way to get a total count or notification as each statement
> is prepared by sqlite_prepare_v2 within sqlite3_exec?
sqlite3_trace_v2() with SQLITE_TRACE_PROFILE is called at the end of each
statement.
Regards,
Clemens
Is there a C API way to get a total count or notification as each statement
is prepared by sqlite_prepare_v2 within sqlite3_exec? The sqlite3_exec
callback interface is silent with respect to CREATE and DROP statements.
Presumably I could copy and paste the entire body of sqlite3_exec into my
6 matches
Mail list logo