Re: [sqlite] Huge numbers of savepoints.

That's just what I was looking for. Thanks, Chris. On Aug 23, 4:36 pm, Doug Currie wrote: > On Aug 23, 2009, at 6:46 AM, Chris Dew wrote: > > > Note: this is not for production code, just an experiment in keeping a > > history of application 'state', allowing current

Re: [sqlite] Huge numbers of savepoints.

On Aug 23, 2009, at 6:46 AM, Chris Dew wrote: > Note: this is not for production code, just an experiment in keeping a > history of application 'state', allowing current state to be > recalculated if an historic input is received 'late'. See >

Re: [sqlite] Huge numbers of savepoints.

With these requirements you can't implement it just on database level because it doesn't fit into the standard savepoint/transaction paradigm of databases. Only committed data and finished transactions will be available after OS crash or to other processes. After transaction is committed it cannot

Re: [sqlite] Huge numbers of savepoints.

Hi, thanks for your questions. 1. restarts or OS crashes should leave the data in a sane state - the last savepoint would be fine. 2. there's no requirement to revert to old savepoints set during a previous application run. 3. no need for more than one process to access the data, though letting

Re: [sqlite] Huge numbers of savepoints.

Apologies for multiple posting - these extra copies were sent from googlemail.com, whereas I has subscribed to the list as gmail.com. Chris. On Aug 19, 8:35 am, Chris Dew wrote: > http://www.sqlite.org/lang_savepoint.html > I'm looking for a datastore with the following

[sqlite] Huge numbers of savepoints.

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

Re: [sqlite] Huge numbers of savepoints.

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

Re: [sqlite] Huge numbers of savepoints.

On Aug 19, 2009, at 3:07 PM, Chris Dew 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 >

[sqlite] Huge numbers of savepoints.

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