I have a few questions about how sqlite3_interrupt interacts with explicit transaction operations. The docs say that "If the interrupted SQL operation is an INSERT, UPDATE, or DELETE that is inside an explicit transaction, then the entire transaction will be rolled back automatically." 1. Can sqlite3_interrupt interrupt a call to BEGIN or its variants (BEGIN IMMEDIATE and BEGIN EXCLUSIVE)? If so, is the transaction automatically "rolled back" in this case? 2. What about an interrupt during an explicit call to COMMIT or ROLLBACK? 3. What is the behavior with regard to savepoints? Will the outermost transaction get rolled back if an operation gets interrupted?
-- Sent from: http://sqlite.1065341.n5.nabble.com/ _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
