I don't think there's anything automatic that will do this. You'd probably be best off with a version field, and just storing the new version with an incremented version id (or timestamp) on each update. Then rolling back would just be a matter of changing some active version flag.
I don't think there's any builtin checkpointing mechanism that would make sense for this kind of "long-term" rollback facility. On Apr 1, 4:18 pm, Sekhar <[email protected]> wrote: > I'm building a wiki-like app that lets multiple users update the data. > Is it possible to use checkpoints with the datastore to protect > against data corruption? E.g., if someone inadvertently deletes a > section we need to go back to a previous state. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
