retrieve entities as they were at a specific revision

[astletron]

I would like to be able to 'snapshot' data by getting all entities as they were at a specific revision number.

One way to achieve this might be to modify AuditReader::find such that a NULL $id parameter results in returning an array of 'latest' (greatest revision number equal to or less then the target revision number and not deleted) entities.

https://github.com/simplethings/EntityAudit/blob/master/src/SimpleThings/EntityAudit/AuditReader.php#L55

Happy to fork and submit a pull request if this approach sounds do-able and the feature is desirable.

[andrewtch]

@astletron , this is implemented by loading 1:M relations. Loading full database without filtering can result in HUGE results sets and not much desirable.

Please close this if relations fixes your issue.

[astletron]

Hiya. Thanks for getting back to me.

Not sure I follow, though. Let me give you an example. I am working on a CMS with a 'publish' workflow. The user modifies content and then pushes a publish button to make the current state live. I would like them to be able to publish historical versions. To do this, I would need to be able to find the state of the database at a particular revision number. Given the current EA interface, I don't think this is possible. Am I missing something?

[andrewtch]

We're actually doing the same thing, that's why I'm making PR's. You can save latest published revision somehow and then load some root entity, all relations will be loaded accordingly. Retrieving full database snapshot is not an option since it can be quite huge and inconsistent.

Given the current EA interface you'll be able to load a particular entity and load all related entites as they were at the point of revision snapshot.

[astletron]

A single entity that existed at some specific revision is not necessarily connected to all other objects that also existed at that time. What I'm after is way to iterate over all objects of all types as they were at a specific revision number.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.