On 6/12/07, womble <[EMAIL PROTECTED]> wrote: > We're a little closer to experimenting with this, and have another question: > is there any coherency checking/row (table?) locking implemented in > django's db layer?
Django itself does not implement any locking features, or anything else designed to manage database concurrency. That's the job of your database -- so long as you're in a transaction you should get a consistent view of the data the whole time you're working with it, and good databases let you configure them to deal with concurrent data changes (e.g., with PostgreSQL you can set transactions to "serializable", and concurrent write attempts from two processes will result in one of them getting an exception saying that the data changed elsewhere). -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
