On 7/29/18, Jürgen Palm <juer...@palm-internet.eu> wrote: > As a quick, ugly workaround for my situation I could add something like > sqlite3_exec(conn1, "SELECT 1",NULL,NULL,NULL); > before the sqlite3_prepare_v2 after the schema change. > > Is there any better way? Or would it be possible to add a SQLITE_PREPARE > flag to sqlite3_prepare_v3, which forces a schema change check?
You only need to do this for sqlite3_column_count(). The sqlite3_prepare_v3() interface might use an obsolete version of the schema, but that will be detected and the prepare will automatically rerun itself at the first sqlite3_step() on the prepared statement. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
