You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we store the history diffs in the direction of v3 -> v2 -> v1. Using this we can only recreate the versions if we have the latest version of the object. When that latest version of the object is deleted from the db it makes the history diffs useless.
To fix this we can reverse the way we store the diffs to "" -> v1 -> v2 -> v3. So we will always be able to recover any version of a record even if we don't have the latest version
The text was updated successfully, but these errors were encountered:
Currently we store the history diffs in the direction of v3 -> v2 -> v1. Using this we can only recreate the versions if we have the latest version of the object. When that latest version of the object is deleted from the db it makes the history diffs useless.
To fix this we can reverse the way we store the diffs to "" -> v1 -> v2 -> v3. So we will always be able to recover any version of a record even if we don't have the latest version
The text was updated successfully, but these errors were encountered: