Question

I started noticing a weird behavior with my SQLite queries for my iPhone application. Whenever I execute an ‘INSERT’ statement, a journal file is created beside my db file (the exact filename is ‘userdata.db-journal’).

If I understand the docs correctly, this journal file is used by SQLite to be able to rollback in case the operation fails. But the file stays there after the operation is completed.

I do the classic steps for preparing, binding and executing the query (no checks for return values for simplicity):

sqlite3 *db = NULL; sqlite3_open( 'userdata.db', &db );  sqlite3_stmt *insertStmt = NULL; const char *query = 'INSERT INTO table VALUES(?,?)'; sqlite3_prepare_v2( db, query, -1, &insertStmt, NULL );  sqlite3_bind_int( insertStmt, 1, 0 ); sqlite3_bind_int( insertStmt, 2, 0 );  sqlite3_step( insertStmt );  sqlite3_reset( insertStmt ); sqlite3_clear_bindings( insertStmt );  sqlite3_close( db ); 

The journal file is created after the ‘sqlite3_step’ function is called and stays there until I close the db. What do I need to do to make it go away?

Answer 1

SQLite by default creates the journal file at the start of a transaction, which is a good thing. Normally it deletes the file upon commit.

You can change this behavior to simply truncate the file (no create/delete necessary) or to zero it, via a PRAGMA sql command. Not all options may be supported on your version of SQLite.

PRAGMA journal_mode = DELETE | TRUNCATE | PERSIST | MEMORY | OFF   

Write operations are normally not completed until you COMMIT, which is implemented by truncating, deleting, or invalidating the journal.

If this behavior is new, I have no explanation for why it might have changed, other than perhaps an upgrade of SQLite changed default behavior, or has become more sophisticated by not reopening the journal for every transaction.