On Sun, 6 Oct 2013 22:58:28 +1000 Paul L Daniels <pldani...@pldaniels.com> wrote:
> "Undark" is only at v0.2 at this time, it's still quite coarse > around some corners and it does not differentiate between > deleted and undeleted rows. It also has a limitation of only > decoding what it finds within the SQLite page (ie, 4K in most > cases), if the row extends beyond the page the data won't be > retrieved ( I am working on this for v0.3 ), finally, it > doesn't decode or dump BLOB data yet, simply not sure how to > represent that sanely on a CSV dump. If Undark decodes the metadata, it might be more useful to create a new database instead of a CSV file. The new database would be a mirror of the input, except that its tables would hold deleted rows (or both deleted and extant, with a column signifying which). That way no information is lost, re-insertion is simple, and representation questions are mooted. --jkl _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
