When SQLite is changing a database, some new data is in SQLite's cache, will other new data has been written to disk. When SQLite is killed in the middle of a transaction, all data in the cache has been lost, so the state of the database will be inconsistent. In that situation, the only option is to roll back the transaction to get back into a consistent state.
The -journal
file actually contains the old data, the new data has been written into the actual DB file.
If you really want to see the changes made by your partial transaction, you can try to delete the -journal
file (which prevents SQLite from doing the automaticlly rollback) and then opening the database, but the state of the database then is inconsistent, so it's likely that you won't be able to access all data.