Re: Data version idea (please discuss)

webb wrote:
> What I am curious about is versioning the data that goes into this
> database using something that I want to call a "checkpoint".  The
> "use-case" would be that you do an insert of something like 100 records,
> updating secondary tables as necessary, check it to the best of your
> ability, then run Function_1.  This function increments the version
> number and returns it, storing whatever is necessary so that Function_2
> can reset the database to any of the version numbers returned by
> Function_1.  I guess there would be a Function_3 that would add tables
> to the checkpointing system.
>
> Questions:
>
> 0.  Does that make sense?

Yes

> 1.  Is there some literature on this, so I don't have to keep bothering
> the list with beginners questions?

Temporal databases - replace mentions of timestamps with version-numbers
and it matches your requirements precisely. There's various stuff on the
web, plenty of academic research and a couple of books too.

HTH
--
   Richard Huxton
   Archonet Ltd