Hi Geoffrey On Tue, May 3, 2016 at 3:42 AM, Geoffrey Martin-Noble <gmngeoff...@gmail.com > wrote:
> Is there a particular reason Django doesn't implement table locks? These > are vendor-specific, but seem to be common to various SQL backends, which > is something Django generally does well. > I’m not aware of any philosophical or technical reason why they haven’t been implemented - as far as I’m aware, it’s simply a matter of nobody has asked for them, and nobody has offered a patch for them. Over the last few years, we’ve been moving away from the Lowest Common Denominator model for the database backends, and towards a general philosophy of “if a database can do it, we will support it”. The only restriction on that is finding an elegant way to express the underlying idea in a way that can be opt-in, and is consistent with existing APIs. Have you given any thought to what the API for a table lock would look like? Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq8486t6cuaivxj6iLoXtUJ1UaNH%2BvyUmNEPeYf1SFO%2B2oWQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
