Does that mean the "prepare" is wrapped inside a transaction?
So you must finalize and re-prepare? Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems ________________________________ From: [email protected] [[email protected]] on behalf of Richard Hipp [[email protected]] Sent: Tuesday, June 26, 2012 9:49 AM To: General Discussion of SQLite Database Subject: EXT :Re: [sqlite] access from 2 different programms to same sqlite3-db On Tue, Jun 26, 2012 at 10:46 AM, [email protected] <[email protected]>wrote: > I have a c++ GUI application from where the db is read and the content is > displayed in a Clistbox. > Then I try to delete some rows from the sqlite3-db from the console. > After rereading from within the GUI the deleted rows are still there. > > How is this possible ? > The GUI is holding a read transaction open. Hence it sees a consistent snapshot of the database from the moment in time when the transaction was started. Subsequent writes to the database are ignored by the GUI until it closes its current transaction and starts a new one. > > ______________________________**_________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users<http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users<http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users%3Chttp://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users>> > -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
