But if the option is between implementing nested transactions without binary journal file compatibility vs not implementing nested transactions at all, I think the user base at large would benefit most from having the nested transaction as an option. A warning could be appended to the docs regarding nested transactions that they are not binary compatible and programs which have the possibility of concurrent access from different versions should not use them. Besides, we're not saying that concurrent access wouldn't work anyways, only that the latest version is required to recover from a crash.
Now I don't know if this is an either-or situation and only these two options are available--break compatibility or not have the feature--but if it is, I personally would vote for having the feature as an option which means compatibility in the case of a crash is also an option. Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] -----Original Message----- From: Darren Duncan [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 10, 2007 5:45 PM To: sqlite-users@sqlite.org Subject: RE: [sqlite] SQLite and nested transactions At 9:20 AM -0400 4/10/07, Samuel R. Neff wrote: >Under what circumstances would an older version of SQLite be >used to rollback a newer journal? Situations I am thinking of include wanting to use multiple application programs with the same database, and each one includes a different version of SQLite due to one being newer than other or some such. Or a user upgrades an application, which as a newer SQLite, then finds the program has problems and they revert back to the older version while waiting for a fix. Think of the SQLite database file like an ordinary user application document; users don't usually expect that editing a document with a newer version of a program will stop them from later editing it with an older one. Sure that happens, but it shouldn't happen any more than necessary. Well, I am mainly thinking about the concurrent use of the database with 2 different applications is the more likely scenario where the backwards compatability would help. -- Darren Duncan ---------------------------------------------------------------------------- - To unsubscribe, send email to [EMAIL PROTECTED] ---------------------------------------------------------------------------- - ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
