A few answers in this thread, replying to no one in particular ... 1. Nested transactions are very useful and should be supported at whatever levels possible.
2. SQLite does not currently support nested transactions, but support for this is on the cards for a near future version, following the implementation of some other important thing. 3. If you want to get prepared for using nested transactions, you should be working now such that autocommit is on by default and you explicitly start and end transactions; then if you use explicit children later, you just do the same thing you've just been doing, but more of it. 4. Any good DBMS will already support atomicity for individual SQL statements. 5. If a DBMS does that, and it supports "transactions", then it does at least one child level already, where each SQL statement is a child. -- Darren Duncan ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
