Use sqlite3_prepare_v2()

When I'm working with SQLite3 databases in Jim, I find that I occasionally
get a 'schema has changed' error so I end up using catch to detect the
error and try the query again.

Here's a quick patch to change the SQLite3 extension to use the
sqlite3_prepare_v2() API function instead of sqlite3_prepare() - trivial
but the _v2() function has a number of benefits and everyone should have a
new enough SQLite3 library to support it. Please can you consider it for
inclusion?

See - http://www.sqlite.org/c3ref/prepare.html

The benefit I'm specifically interested in is:

With the _v2() variant, "If the database schema changes, instead of
returning SQLITE_SCHEMA as it always used to do, sqlite3_step() will
automatically recompile the SQL statement and try to run it again."

1 files changed, 1 insertions, 1 deletions

diff --git a/jim-sqlite3.c b/jim-sqlite3.c
index 8016b7f..62d8fa9 100644
--- a/jim-sqlite3.c
+++ b/jim-sqlite3.c
@@ -193,7 +193,7 @@ static int JimSqliteHandlerCommand(Jim_Interp *interp, int argc, Jim_Obj *const
         query = Jim_GetString(objPtr, &len);
         Jim_IncrRefCount(objPtr);
         /* Compile the query into VM code */
-        if (sqlite3_prepare(sh->db, query, len, &stmt, &tail) != SQLITE_OK) {
+        if (sqlite3_prepare_v2(sh->db, query, len, &stmt, &tail) != SQLITE_OK) {
             Jim_DecrRefCount(interp, objPtr);
             Jim_SetResultString(interp, sqlite3_errmsg(sh->db), -1);
             Jim_Free(nullstr);