On 2 Mar 2012, at 6:16pm, Steffen Mangold <steffen.mang...@balticsd.de> wrote:
>> There's no magic tool for repairing damaged database files. But by using >> the .dump command (if necessary on each individual table and view) then >> creating a new database file and using the .read command you can often >> rescue some or all of the data in the original > > database. >> > > Ok, with .dumb i now created a "db.sql" file successfully. Is it very long ? Can you read it with a dump utility or a text editor (don't try it with a word processor) and see the SQL commands in it ? > but I don't get the read command!? How create a new DB file with that command? > With "sqlite> .read db.sql" it does much reading but no file is created. Start the shell tool supplying it with the name for a new blank database file (I think you were using fred.temp in your earlier example). Then do a '.read db.sql'. prompt$ sqlite3 db.temp SQLite version 3.7.7 2011-10-10 22:11:44 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> .read db.sql Then do something like a '.schema' and see if it has created the tables you expected. Then quit the shell tool using '.quit' and see if the file you created exists. Are you saying it creates a database file but doesn't put anything into it (zero filesize) or that it doesn't even create a blank file ? Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
