Thanks. I'll look into this path and see if it fits. Anybody here live in the Irvine, Ca area. After the discussions on this subject I have come to the conclusion that we need somebody to implement our embedded database. Ray
---- Gerry Snyder <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > Here is an excerpt from my requirements doc: > > > > .... > > If a transaction is aborted all database state is reset > ("rolled-back") to its value at the time the transaction was opened. > > Nested transactions abort or commit relative to their > parent transaction. In the case of an aborted transaction, > the database state is rolled back to the point where > the transaction was started. (This is true whether > or not the transaction is nested.) In the case of > a commit, the nested transaction’s changes become > part of its parent transaction, as if the nested > transaction boundaries had never been established. > > If I had to implement this with the current SQLite, > I would start a new TEMP table at each BEGIN, and > destroy the current TEMP table at a ROLLBACK or > add its contents to its parent table (either > the previous TEMP table or the "real" table at a > COMMIT. > > I think that does everything you need, and would be > easy to program. > > HTH, > > Gerry > > ----------------------------------------------------------------------------- > To unsubscribe, send email to [EMAIL PROTECTED] > ----------------------------------------------------------------------------- > ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------