What are the recovery consequence(s) to a database (journal mode wal) should a master-journal file be lost?
Suppose a flash sensitive embedded product had to update its database every second. To save flash wear the database (journal mode delete) is created in ram (e.g. /tmp). Suppose every 8 seconds there had to be a transaction across the ram database to not only update it but also to sync with another database in flash (journal mode wal). Both databases must be updated and sync'd atomically, a.k.a one transaction. Flash cannot afford to have an mj file created/deleted every 8 seconds. So, assuming... -The ram db connection attaches the flash db -Transaction is started and mj file created in ram -Ram and flash databases are modified -On power failure the flash db's wal file is flushed (persists reboot) however the mj transaction never commits and the ram db and mj file are gone (they're in ram after all). Ideally, on reboot the flash database will recover via its wal file, the ram db will be recreated and back in business. Obviously the product can afford to lose the ram db and the previous 8 seconds of data, but does losing the ram db with the corresponding mj file have recovery consequences for the flash db and its wal file? Thanks. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
