I haven't dug into this code enough to see how possible or necessary this is, so apologies if this issue isn't fully formed.
As I understand it, this project is good for tracking a set of records as they change in time. I'm curious about tracking a set of records as they did change in time, even if I'm doing the updates at a later time.
For example, I have a data set of changing objects on a blockchain, but I'd like to put them in a database that actually, you know, works. The changes have already occurred, but I want to track those past changes by batch-extracting from the blockchain and inserting the changes into a local SQLite db. It's the time those changes occurred, not the time that I'm updating the DB, that I care about in this case.
It looks like this might involve some nontrivial shuffling around of things and a slightly different use case-- updates would include a normal DB row and an (optional?) timestamp that would be used as the _update value.
Still, might be useful to allow an arbitrarily-timed sequence of updates as opposed to a live-updated one. I might take a swing at a PR if you'd be interested.
I haven't dug into this code enough to see how possible or necessary this is, so apologies if this issue isn't fully formed.
As I understand it, this project is good for tracking a set of records as they change in time. I'm curious about tracking a set of records as they did change in time, even if I'm doing the updates at a later time.
For example, I have a data set of changing objects on a blockchain, but I'd like to put them in a database that actually, you know, works. The changes have already occurred, but I want to track those past changes by batch-extracting from the blockchain and inserting the changes into a local SQLite db. It's the time those changes occurred, not the time that I'm updating the DB, that I care about in this case.
It looks like this might involve some nontrivial shuffling around of things and a slightly different use case-- updates would include a normal DB row and an (optional?) timestamp that would be used as the
_updatevalue.Still, might be useful to allow an arbitrarily-timed sequence of updates as opposed to a live-updated one. I might take a swing at a PR if you'd be interested.