-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Full versioning for Records and RecordTypes #80
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One very cool part of Ashlar is that the schemas are all versioned under the hood, meaning that a developer using Ashlar can expose a full audit log of how a schema has changed over time and potentially allow an admin user to roll back to previous versions.
I wonder how much leverage we could get from implementing a similar versioning system for Records and RecordTypes. Records and RecordTypes are already append-only in that they use
active
andarchived
flags (respectively) to indicate whether or not they've been deleted, but to my knowledge we don't preserve previous versions when someone edits them.Allowing full versioning would have some advantages:
Full versioning would also have some disadvantages:
(This isn't a pressing issue -- just filing it here for future discussion. Feel free to tag at will!)
The text was updated successfully, but these errors were encountered: