I'm mainly referring to this quote.
So, you can lose committed transactions too.
21 karma · joined November 18, 2021
I'm mainly referring to this quote.
So, you can lose committed transactions too.
> In NORMAL mode, the database engine syncs to disk only at critical moments (e.g., during checkpoints) rather than at every single transaction commit. In WAL mode, this is completely safe from database corruption; even if the server crashes, only the uncommitted transactions in the WAL are lost, but the database integrity remains intact.
No, this is not safe. You can lose the latest committed transaction with this pragma.
"In WAL mode, SQLite exhibits "snapshot isolation".
When a read transaction starts, that reader continues to see an unchanging "snapshot" of the database file as it existed at the moment in time when the read transaction started.
Any write transactions that commit while the read transaction is active are still invisible to the read transaction, ..."
I needed:
- app groups to easily enable/disable group of programs - wildcards in program path names - efficient IP addresses blocking, as in PeerBlock - speed limiting - auto-apply program's rules to its child processes - control SvcHost services by service names - traffic statistics history
2. https://github.com/tnodir/luaplsql - LuaPlSql is a Lua Plug-In framework for PL/SQL Developer IDE.
I used it 10 years ago to write scripts in IDE for Oracle DB.