Periodical versions clean-up about doctrineextensions HOT 4 CLOSED

hm, maybe there could be few strategies on how the logs should be stored.

• aggresive, stores every versioned field, does not care about changeset
• default, current behavior, stores only changedset

Or by default it could just not care about a field which is not in revision list. This option could probably be configurable.

Any other ideas? Whats your opinion?

from doctrineextensions.

After some thinking, I afraid that you must have all revisions to make "revert" work properly with changeset-based strategy.

Otherwise you'll get inconsistent behavior: sometimes objects will be reverted to expected state, but sometimes you'll get object in mixed state. E.g. blog post "title" is restored, but "text" remains in current state, because older revision, which contained last "text" change was deleted.

Possible workaround is to merge changesets from revisions, which you are going to delete, but that makes maintenance rather complex.

I'd prefer aggressive strategy, because it is way simpler to maintain (both code and data). Of course it will take more disk space, but that shouldn't be a problem - you may enable compression for this data on RDBMS level and probably one day in MongoDb too.

But if using this approach it would be still useful to know which fields were modified in this revision, as it's the cool feature, which changeset-based strategy has.

What do you think?

from doctrineextensions.

I think that I should think about all those mentioned issues and when we should decide which solution is best to implement. I think I'll add an option to Loggable annotation, to configure either to store all versioned fields all the time or only the changeset. The full storage would require additional flag or something to identify which fields were changed in this specific log entry. Anyway I need to rethink it more

from doctrineextensions.

solved it in simple way, which is: do not trigger exception when the object is not fully reverted, references #163

from doctrineextensions.