The busy timout should tell the Sqlite driver to wait to acquire locks
instead of aborting immeadiately.
The Write-Ahead Logging mode should make parallel accesses to the
database more efficient. https://www.sqlite.org/wal.html
There is no need to initially set the database version to 0, returning 0
is enough to run the appropriate migrations.
This will partially fix#80. The underlying problem is probably a
temporary database lock that causes an exception in getOpt(). This still
needs to be addressed.
This is what the old query methods allowed. Passing in an array is still
somewhat cleaner, but allowing separate arguments should make porting
older code a bit more convenient.
Even though mutliple statements can be passed to $sth->execute(),
failures will only be checked in the very first statement. Failures
later on will lead to the rest of the statements to be silently ignored
rendering our rollback strategy moot.
We now always split multiline statements and run them separately
(affects import and migrations).
The export was adjusted to not include the transaction handling and
fix entry exports.
