less noise: simplify db_remove_reset()
db_remove_reset() needs to be called after each stmt run, whether it succeeded
or not.
In case sqlite3_clear_bindings() would fail to unbind a stmt, we would anyway
be beyond recovery. There seem to be no plausible situations where such failure
would occur, unless there have been no bindings in the first place.
In case there was an SQL stmt failure, sqlite3_reset() will re-barf the same
error message, we will always have logged it earlier already in the proper
context.
We are never evaluating the return value, nor would we know how to recover from
non-success.
The conclusions:
- db_remove_reset() does not need to log any errors.
- db_remove_reset() does not need to return success.
Change-Id: I21678463e59f607f5f5c5732963e274392f0fffd
diff --git a/src/db.c b/src/db.c
index 7c25e63..179eba8 100644
--- a/src/db.c
+++ b/src/db.c
@@ -70,20 +70,10 @@
}
/* remove bindings and reset statement to be re-executed */
-bool db_remove_reset(sqlite3_stmt *stmt)
+void db_remove_reset(sqlite3_stmt *stmt)
{
- int rc = sqlite3_clear_bindings(stmt);
- if (rc != SQLITE_OK) {
- LOGP(DDB, LOGL_ERROR, "Error clerearing bindings: %d\n", rc);
- return false;
- }
-
- rc = sqlite3_reset(stmt);
- if (rc != SQLITE_OK) {
- LOGP(DDB, LOGL_ERROR, "Error in sqlite3_reset: %d\n", rc);
- return false;
- }
- return true;
+ sqlite3_clear_bindings(stmt);
+ sqlite3_reset(stmt);
}
/** bind text arg and do proper cleanup in case of failure. If param_name is