aboutsummaryrefslogtreecommitdiff
path: root/src/main.c
diff options
context:
space:
mode:
authordrh <drh@noemail.net>2018-04-28 12:43:16 +0000
committerdrh <drh@noemail.net>2018-04-28 12:43:16 +0000
commit7df011969cd56cee9336770b6ad9c4828e33a3b6 (patch)
tree22c58c903dbcda564400db00a01f530da1c50a09 /src/main.c
parent46462e35d3731ef793de495c6cd723fbf8820e07 (diff)
downloadsqlite-7df011969cd56cee9336770b6ad9c4828e33a3b6.tar.gz
sqlite-7df011969cd56cee9336770b6ad9c4828e33a3b6.zip
Add the SQLITE_DBCONFIG_RESET_DATABASE control as a replacement for
the reset_database pragma. Resetting the database should be hard enough to do that it cannot be done by accident. FossilOrigin-Name: ff836cb8b0377c5970ecb2b797702e2b5d208eda443ecbd55f4c238a3094b28a
Diffstat (limited to 'src/main.c')
-rw-r--r--src/main.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/main.c b/src/main.c
index 442067a14..d23f9afcf 100644
--- a/src/main.c
+++ b/src/main.c
@@ -834,6 +834,7 @@ int sqlite3_db_config(sqlite3 *db, int op, ...){
{ SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE, SQLITE_NoCkptOnClose },
{ SQLITE_DBCONFIG_ENABLE_QPSG, SQLITE_EnableQPSG },
{ SQLITE_DBCONFIG_TRIGGER_EQP, SQLITE_TriggerEQP },
+ { SQLITE_DBCONFIG_RESET_DATABASE, SQLITE_ResetDatabase },
};
unsigned int i;
rc = SQLITE_ERROR; /* IMP: R-42790-23372 */