So Django keeps a connection open from view-to-view? If so, db level locking should work, but I thought a transaction was started on going into a view, and commited/rolled-back on exit. If the later, then I don't think James' idea will work. Am I missing something?
Thanks, Julian On Jun 22, 8:53 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > On 6/22/07, ToddG <[EMAIL PROTECTED]> wrote: > > > Rails has an implementation you could look at for an example, likely > > simpler to read than something like Hibernate... not sure how/if > > anything could be hooked/monkey'd into the django-admin though. > > This is best handled by your database (assuming you're using a real > database); set the appropriate transaction isolation level, and your > DB will helpfully toss back an exception if you try to edit something > that's changed since you retrieved it. > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
