-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/03/12 14:45, Steffen Mangold wrote: > I'm happy now and enter command ".exit" and bam Db file has 0kb?!?!? > What have i done wrong? Any Commit command or something?
What you don't seem to understand is that your original database is corrupt. The data that is in it is not exactly what SQLite (and hence your program) put in it. While doing the dump, the corruption was discovered and the dump aborted. You just replaced the abort command with "save what we have so far". There is no way for SQLite to recover what is changed/missing/corrupted. You'll need to work out what the damage has been. The integrity check only examines the top level structure - it does not detect data changes (mostly). For example if every 'a' had been changed to a 'b' it would not detect that. You should also work out how the corruption happened since you really don't want it to happen again. Here is how to corrupt a SQLite database: http://www.sqlite.org/howtocorrupt.html Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk9RVc8ACgkQmOOfHg372QQQ3gCfZBxh6oxaZ2OXhYDB9xsK7+BT 38IAnj7aiKugfj1w6/L1GbWfvkAsAz9/ =wWdx -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
