Re: [sqlite] Please review this email to sqlite's mailing list

2012-05-16 Thread Charles Samuels
On Wednesday, May 16, 2012 1:28:17 e.h. Simon Slavin wrote: > On Tue, May 15, 2012 at 1:55 PM, Charles Samuels wrote: > > At some point, we get a checkpoint; at this instant, what is in otherdb > > and what is in sqlite is what we want committed to sqlite, if either of > > them fails, we can rollba

Re: [sqlite] Please review this email to sqlite's mailing list

2012-05-16 Thread Simon Slavin
On Tue, May 15, 2012 at 1:55 PM, Charles Samuels wrote: > At some point, we get a checkpoint; at this instant, what is in otherdb and > what is in sqlite is what we want committed to sqlite, if either of them > fails, we can rollback both of them and both databases return to a > consistent > state

Re: [sqlite] Please review this email to sqlite's mailing list

2012-05-16 Thread Charles Samuels
On Wednesday, May 16, 2012 11:33:02 f.h. Igor Tandetnik wrote: > Well, SQLite doesn't. Basically, you want SQLite to maintain multiple > not-yet-committed versions of the same record. Well, yes, but it already does; you can rollback a savepoint. If I could rollback a savepoint and then unrollbac

Re: [sqlite] Please review this email to sqlite's mailing list

2012-05-16 Thread Igor Tandetnik
On 5/15/2012 1:55 PM, Charles Samuels wrote: The question here is: where can I put that "more data" so that it won't be part of checkpoint 1, but is still accessable by sqlite select statements? (Accept that otherdb allows asychronous commits such that I can add more data to it that doesn't wind

Re: [sqlite] Please review this email to sqlite's mailing list

2012-05-16 Thread Charles Samuels
On Wednesday, May 16, 2012 10:00:37 f.h. Adam DeVita wrote: > Did you check out > http://www.sqlite.org/inmemorydb.html > > Could you use an in-memory db to act as a db for a save point? Yes, but this is incredibly hard: I have to maintain the schema twice, I can't allow the user to enter their

Re: [sqlite] Please review this email to sqlite's mailing list

2012-05-16 Thread Adam DeVita
Did you check out http://www.sqlite.org/inmemorydb.html Could you use an in-memory db to act as a db for a save point? When you are ready to commit, do so from 1 in memory db, while accumulating into another in preparation for that save point. Adam On Tue, May 15, 2012 at 1:55 PM, Charles Samue

[sqlite] Please review this email to sqlite's mailing list

2012-05-15 Thread Charles Samuels
I'm using sqlite in addition to another database ("otherdb") storing data in a specific manner. I'm trying to keep atomicity of my disk commits. It can take several minutes for otherdb to commit, and while it commits it can already start accumulating data for a future transaction. Some of the