If you read over the linked discussion it's quite possible, just an issue of how disruptive it would be to the ORM APIs.
On Saturday, June 30, 2012, Dennis Lee Bieber wrote: > On Sat, 30 Jun 2012 15:24:59 -0700 (PDT), ydjango > <neerash...@gmail.com<javascript:;> > > > declaimed the following in gmane.comp.python.django.user: > > > > > I did google search on "optimistic locking". Most discussion are very > old. > > > > Has Django added any features to support it or what are folks generally > > doing? > > Since the locking relies upon the database engine itself, Django > probably can't do anything for it -- it would require the front-end to > know about features of the engine, and that could be a significant > impact if one changes the engine later (not to mention the overhead of > looking up some feature list for each engine so it can execute different > code based on what type of locking is available). > -- > Wulfraed Dennis Lee Bieber AF6VN > wlfr...@ix.netcom.com <javascript:;> > HTTP://wlfraed.home.netcom.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<javascript:;> > . > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com <javascript:;>. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- -- Steven -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
