Steffen Mangold wrote: > > I have a question to the System.Data.SQLite in action with the .Net > TransactionScope. In the SQLite documentation is written that the > default behavior of a transaction in case of an error is "ABORT". > In documentation is also writen that "prior SQL statements within > the same transaction are preserved and the transaction remains > active". >
I believe that I've found and fixed an issue in the SQLiteConnection class that could be responsible for the errant behavior you are seeing. The check-in is here (on the "bug-ccfa69fc32" branch): http://system.data.sqlite.org/index.html/ci/42af4d17a5 Would it be possible for you to update your local System.Data.SQLite and see if this fix corrects the behavior you are seeing? The fix is located on the "bug-ccfa69fc32" branch in Fossil. If you need information on checking out or building the System.Data.SQLite source code, please let me know and I will send complete step-by-step instructions. -- Joe Mistachkin _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
