On Wed, Oct 1, 2008 at 5:25 PM, David Hall <[EMAIL PROTECTED]> wrote: > > I've just released an open-source version control application for > Django. It is available for download from Google code. > > http://code.google.com/p/django-reversion/ > > Features include: > > - Roll back to any point in a model's history - an unlimited undo > facility! > - Recover deleted models - never lose data again! > - Admin integration for maximum usability. > - Group related changes into revisions that can be rolled back in a > single transaction. > - Automatically save a new version whenever your model changes using > Django's flexible signalling framework. > - Automate your revision management with easy-to-use middleware. > > It can be easily added to your existing Django project with an > absolute minimum of code changes. > > It's so far been previewed by a half dozen developers, with good > feedback. I'd appreciate any comments / suggestions you may have to > offer.
How does django-reversion deal with relationships between Django models? Version-controlling relationships between entities is an Achilles heel of such applications. I have read django-reversion docs on google code wiki, but I couldn't find any information on that matter. -- Marek Stępniowski http://stepniowski.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
