Another approach to version controlling the content in your Django database. This one looks remarkably good, at a glance. It stores revisions in the database, rather than an external version control system, and can be added to an existing project with just a few lines of code (and no modifications to your existing models). Looks very slick. I only have one question: what happens when you make a schema change to a versioned model (i.e. add/change/delete a field)? I’m going to assume this would render the versioned content unusable, but I’m not sure about that. Anyone know?
No one has posted any comments on this entry as of yet. Perhaps you’d like to be the first?
Post your comment