[EMAIL PROTECTED] wrote: > It is also highly inefficient for Web applications (since > they most often do nothing transactional) and gets you into trouble in > error cases.
I don't want to get into the argument about ticket 3460 itself but I just don't get this paragraph... What is special in web applications that makes them not require transactions? And more, how transactions -- a mechanism for preventing DB to end up in an inconsistent state -- can get you into error cases? FWIW, we're developing a typical web service[1] that, basically, lets people to say "I'm going to this event". And we rely on transactions very much because we heavily use denormalized data like keeping count of people for an event. The only sane way of making sure that those stored counts are sync'd to real counts of people in another table is to do changes to them in a single transaction. It's just one example anyway... [1]: http://kuda.yandex.ru/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
