> The WAL file does not store a bunch of DELETE FROM statements. The WAL > file stores 4k pages of the database file as they will appear after the > delete occurs. Details at http://www.sqlite.org/fileformat2.html > So, no, there is no way to do what you are asking
Is there, instead, a method for extracting the pages marked for ignore from the DB/ WAL / SHM files and manually piecing back together, or issuing a directive to alter the relevant page markers from "ignore" to their previous state? This article implies there is: http://digitalinvestigation.wordpress.com/2012/05/04/the-forensic-implications-of-sqlites-write-ahead-log/ That said, I'm guessing it would be a non-trivial task even for a seasoned DB programmer... The only other way I can see out of it would be to create a dummy SMS DB (e.g. with one test SMS), then use this method to create a XML template to use with SMS Backup / restore, manually piecing the XML file togther using data extracted with carefully-chosen* GNU strings parameters: http://forum.xda-developers.com/showthread.php?t=1585957 http://forum.xda-developers.com/showthread.php?t=1683608 That or stump up the 250 GBP for Epilog SQLite analysis ;) M *At least it looked that way when running the SHM file through strings _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
