But how do you expect your application to deal with restarts and/or OS crashes? Do you want to still be able to revert to "marks" set in previous application run or not? And what about accessing to the data stored between "marks" from other processes?
Pavel On Wed, Aug 19, 2009 at 4:07 AM, Chris Dew<cms...@googlemail.com> wrote: > http://www.sqlite.org/lang_savepoint.html > I'm looking for a datastore with the following properties: > * I need to 'mark' the state frequently (sub second interval). > * I need to be able to revert the datastore to a previous mark (with no > appreciable delay). > * I only need to keep the last few hundred 'marks'. (i.e. I never need to > revert to a datastore marked more than a few minutes ago.) > > The savepoint functionality in sqlite looks to almost fit the bill, but its > savepoints seem to be nested - i.e. you cannot 'forget about' old savepoints > while retaining recent savepoints. Is my understanding correct here? I'm > concerned that this would cause a performance issue when millions of nested > savepoints have accumulated. > > Obviously I can roll my own data structure here, but is sqlite was feasible, > it would be good. > > Does anyone have any suggestions? > > Thanks, > > Chris. > > -- > > http://www.finalcog.com/ > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
