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.
This is similar to how Hibernate works. Because developers have to manually add to their Model classes the 'versioned' attribute (in whatever form is appropriate) it automatically implies that such feature is off by default. I think it wouldn't even be very hard to do, but it would be best to do so on the magic-removal branch and I have never looked at that yet. The real tricky bit is to make it work together with the Forms and Manipulators, since you need a way to store and retrieve the row-version field to carry it over from the current HTTP request to the next. I haven't yet figured out the most satisfying way to do that (hidden form variables are rather ugly for this purpose, and inherently unsafe). But I'm not one of the Django devs and I have no idea what thoughts they might have on the implementation of row-versioning or row-locking features. Cheers, --Tim -----Original Message----- From: django-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of DavidA Sent: woensdag 1 maart 2006 12:51 To: Django users Subject: Re: Django in a Load-Balanced environment (ORM issues) ... I just want to echo Peter and Ivan's sentiments on NOT making this default behavior. What attracted me to Django was a simple, fast, elegant framework for quickly building common types of web applications. I've wandered into the tarpits of J2EE in my past life and I was looking for something at the other end of the complexity/usability spectrum. Django is just that. I'd hate to see the project bog down focusing on features that consume 80% of the dev resources and are useful to only 20% of the community. And certainly if this type of functionality is ever added it should be completely separate and off by default. Sometimes less is more. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
