>That's good to know, but as you have stated previously, transactions >alone won't solve this problem. There still needs to be some concept of >versioning on top of the transactions, which isn't trivial >(arguably/perhaps even harder to do right than supporting transaction >wrappers).
As Adrian wrote, that's currently not in the scope of Django. But if you write some code for that, you might want to share it with others. It shouldn't be too hard if you restrict your models with regard to layout of fields - for example allways name that version field "version" and put the code to prevent writing outdated objects into the .save() of the model class. Oh, and transactions actually will solve a very large part of those problems, because within a transaction a database makes sure that others won't stomp on your data, either by implicit locking, versioning or exception-raising. So only stored objects outside of transactional control will pose problems, and I think in those cases it's fine for Django to assign the duty of integrity checking to the programmer. So, no, we don't need another ticket, we just might need some sample code by someone who needs this feature ;-) 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 -~----------~----~----~----~------~----~------~--~---
