Optimistic Locking in Django?

[ydjango]

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?

[Steven Cummings]

I started looking into it a while back: https://code.djangoproject.com/ticket/16549

The work broke down into ensuring that the updated/deleted/matched counts were returned from the internal ORM objects. Then there was a fair amount of discussion of what the public API of the ORM could provide on top of that. It's kind of died out a bit, I'd like to get back to it and rekindle the discussion when I can find some time.
--
Steven

On Sat, Jun 30, 2012 at 5:24 PM, ydjango <neera...@gmail.com> wrote:

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?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/oaykVwXK58wJ.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to django-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

[Steven Cummings]

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 <neera...@gmail.com>
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
       wlf...@ix.netcom.com    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...@googlegroups.com.
To unsubscribe from this group, send email to django-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

--
--
Steven