On 2 Mar 2012, at 7:08pm, Steffen Mangold <steffen.mang...@balticsd.de> wrote:
> Ok maybe i found it in the sql file is written (file end): > > [...] > INSERT INTO "InverterData" VALUES(2478,'2012-02-28 > 15:00:00',1435.73,429173.78,170.28,170.75,169.38,397.56,397.38,396.69,NULL,210976,31,NULL,NULL,1,304,NULL,NULL,NULL,694,NULL,NULL,NULL); > /**** ERROR: (11) database disk image is malformed *****/ > /**** ERROR: (11) database disk image is malformed *****/ > CREATE TRIGGER SensorData_InsertUpdate > [...] > ROLLBACK; -- due to errors > > So sqlite shell can not understand "/**** ERROR: (11) database disk image is > malformed *****/" I think. > and make a rollback? > > Do you think that's it? Yes, that's probably what's causing the errors. If you remove those lines (or perhaps just the ROLLBACK) from the text file then you might get a successful '.read' session. But what it means is that the original database ... the one you did a '.dump' of, was so corrupt that the shell tool couldn't dump it to a text file successfully. So your .sql file may not be any use since it is missing at least some of the data, perhaps an entire table or some other structure. If you need absolutely complete data from it you may need expert help in trying to rescue data from the original database file. On the other hand if you understand the data structure yourself you might be able to patch it up to a state good enough to let you continue. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
