Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
When saving new revisions for every change, we end up with a lot of duplicated data on a site. This is a good things because it gives you a full audit trail, however it also means a much larger database. Rather than performance issues as such, it tends to increase database dump and restore times first.
Proposed resolution
Consider providing a way to 'prune' older revisions. We could add a 'minor revision' flag similar to wikipedia's, or trim by age, or trim by the number of revisions in the past for a particular entity.
Could also decide we don't want this in core and defer the logic to a contrib module.
Comments
Comment #2
catchComment #4
hchonovThere is also another option - saving only the changes between the different revisions instead of saving everything on a new revision. Like an incremental backup. What do you think?
Comment #18
catch