Hi Simon, first nice to hear from you. :)
> Fred helps solve Helen's problem one day, Helen may solve Fred's the > following week. Oh I'm not mean pro support. What you descript is what I'm searching for. Like a forum. > Can you show us a pointer to this information ? Sure, http://www.sqlite.org/lang_transaction.html " Such transactions usually persist until the next COMMIT or ROLLBACK command. But a transaction will also ROLLBACK if the database is closed or if an error occurs and the ROLLBACK conflict resolution algorithm is specified. See the documentation on the ON CONFLICT clause for additional information about the ROLLBACK conflict resolution algorithm." http://www.sqlite.org/lang_conflict.html " ABORT - When an applicable constraint violation occurs, the ABORT resolution algorithm aborts the current SQL statement with an SQLITE_CONSTRAIT error and backs out any changes made by the current SQL statement; but changes caused by prior SQL statements within the same transaction are preserved and the transaction remains active. This is the default behavior and the behavior proscribed the SQL standard." I think "transaction remains active" make it sure and there will be not rollback at all. > Transactions are a way of grouping database changes together. > Your description above seems to say something different. If you trying this in a DB Sqlite tool (or command shell) you see the behave I described. Greetings from germany, Steffen _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
