latest usage of those error codes. Modify sqlite3_open_v2() so that it does
return a valid sqlite3 object in the event of SQLITE_MISUSE due to bad
open flags, so that sqlite3_errmsg() does not report "out of memory" in that
case.
FossilOrigin-Name: f27b6370407842e2c175ea4aa9ce018723c57eaac0cccc1f8399bc20f33324be
(since the DROP might fail after sqlite_master changes). Also make
sure statement journals are initiated if there are pending SELECT
statements. Ticket #2820. (CVS 4591)
FossilOrigin-Name: bf34284ff0c60ae6e735e09bb29cd48b158e8dce