On Tue, Sep 09, 2008 at 04:55:01PM +0200, Lothar Behrens scratched on the wall:
> I prepare an insert statement and bind the parameters that afterwards > get executed with sqlite_step(). This function then returns SQLITE_DONE > and I prepare a new select statement wich let me display the just > inserted data in my database forms (database file not closed while > that). > Does someone have any more ideas how to narrow the problem ? > (After the insert statement until to closing of that file) Everything you describe sounds exactly as if a transaction has been started, but is not committed. When you close the database, the transaction is automatically (and correctly) rolled back. This will also delete the journal file. I know you said you weren't trying to start a transaction, but you might double check that. Set a breakpoint right after the INSERT is finished and check to see if you have a journal file or not. You could also try issuing a "BEGIN" right after the INSERT. If you get an error, you're already inside a transaction. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "'People who live in bamboo houses should not throw pandas.' Jesus said that." - "The Ninja", www.AskANinja.com, "Special Delivery 10: Pop!Tech 2006" _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users