> Im observing that, if for example an SQL command in a transaction is > uncorrect, the rollback does not work: the previously inserted records are > not removed.
If you are trying to execute an incorrect SQL statement this statement is not executed but transaction is not rolled back automatically. You have to execute ROLLBACK or COMMIT after that by yourself. Pavel On Fri, Jan 20, 2012 at 8:07 AM, Marcello Botrugno <marcello.botru...@dedalus.eu> wrote: > Hi all, > I am new of SQLite and I am developing a multithread application using > SQLite 3.7.9 on MS Windows. > I am using the precompiled version of SQLite downloaded from www.sqlite.org. > > Each thread of the application, opens a private connection to the database. > > Im observing that, if for example an SQL command in a transaction is > uncorrect, the rollback does not work: the previously inserted records are > not removed. > > Executing from sqlite3.exe the command: > PRAGMA compile_options; > > I get the following data: > ENABLE_FTS3 > ENABLE_RTREE > TEMP_STORE=1 > THREADSAFE=0 > > I deduce that the library I am using is not thread safe. > I don't know if the behavior of rollback depends on this but I should like > to use a version of SQLite copiled with THREADSAFE=1. > Do know if I need to compile the library by myself or is it possible to get > a precompiled version of SQLite (threadsafe) somewhere ? > > Thanks for any help. > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
