>They way I would enivsage adding this functionality to Django would be >that in your model you specify, for each Model object (=table), that it >is to be versioned. Versioning would automatically add a '_version' >column to the generated DDL, and the standard Django save() routines >would take care of atomically checking and incrementing the row-version >and throwing exceptions if updates fail because of concurrent changes.
The right way to add this is to wait for magic-removal and then just use a Mixin class to add that functionality to all models where you need it. And in that case this mixin class might even be something we would want to include into django.contrib somehow, so that it's a readily available solution for others. bye, Georg --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
