Database modeling for Google engine for multiple object revision

Question

in my application (wiki-wiki view) - the article often changes.

and I need to track all the changes that were made in this article. {text only. }

one rough way I've done is to add a datetime property and create a new object every time something changes. that too much depletes the database. {as well as unnecessary index waste too. }, and you also need to recreate the parent-child relationship and the entity.

I also have a journal that can show the changes, but I want something easier, so switching from one version to another is easier.

ideas?

thanks.

Answer 1

You can share the location on your wiki from the content and the link from there to the page version. Keep versions in a linked list, double-tied if you use bidirectional navigation, circular, any.

Parent child, indexing, etc. deal only with the location and article related to it. Reverting to a previous change only changes the link in the location (and pushes the changes to your indexing machine). Cropping is the operations with the base list, i.e. Pointing the next field to the version below and deleting the version between them.