I hadn't thought about limiting the amount of data in the revisions
table(s). On one hand, that should be easy to add an attribute to
specify that. On the other hand, I am not sure when the deletions
should take place. I suppose it would have to run a delete SQL
statement every time that it added a record (or at least check if one
should be run every time). I think it could track the last time it did
it and only run the SQL if it hadn't been run in X # of inserts or X #
of day (depending on whether the limit was in time or in records).
Yeah, I was definitely thinking that restoring should be to a specific
revision and not necessarily just to the previous state.
I *think* it should be easy to have DataMgr retrieve records from a
revisions table just like it would from a normal one. I'm not sure if
it should be allowed to modify it directly, however.