> > Anyways, as concurrency is hard and taking row level locks is cheap > and easy way to get the concurrency right I would suggest you use the > select for update method. Also, this way you will avoid the need to > retry failed transactions because of concurrent updates. > > IMHO, both approaches are valid and have their own advantages and disadvantages. I don't think that we have enough information to make a suggestion. What works best for the situation is for the OP to decide.
Regards, Tamas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
