lib-sql/driver-sqlite: Ensure tail is handled correctly in driver_sqlite_statement_init()

This is not likely to happen, but satisfies static analysis.

diff --git a/src/lib-sql/driver-sqlite.c b/src/lib-sql/driver-sqlite.c
index 594358f49af28b58f92fe5483fe7df2ab4a57ba0..c51ada8756fa3b9cd469c03c0b576619622ca5a6 100644 (file)
--- a/src/lib-sql/driver-sqlite.c
+++ b/src/lib-sql/driver-sqlite.c
@@ -575,6 +575,7 @@ driver_sqlite_statement_init(struct sql_db *_db, const char *query_template)
 
        if (driver_sqlite_connect(_db) < 0) {
                stmt->rc = db->connect_rc;
+               tail = NULL;
        } else {
                stmt->rc = sqlite3_prepare_v2(db->sqlite, query_template, -1,
                                        &stmt->handle, &tail);
@@ -583,7 +584,7 @@ driver_sqlite_statement_init(struct sql_db *_db, const char *query_template)
                stmt->error = p_strdup(pool,
                                       driver_sqlite_result_str(_db,
                                                                stmt->rc));
-       } else if (*tail != '\0') {
+       } else if (tail != NULL && *tail != '\0') {
                stmt->error = p_strdup_printf(stmt->api.pool, "'%s' unparsed",
                                              tail);
                stmt->rc = SQLITE_ERROR;