Hi, in the past I've written to this list re using the django db back-end as a db access layer for a test-automation system I work on; we hope to re-write the current front-end with django at some point.
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? i.e. if I have two scripts, on two different machines, both accessing the same db & table, what built in support is there to catch race-conditions/invalid updates/etc? Are there any examples out there someone can point me to? Also, is there any difference with which db is used- MySql vs Postgres? So far we've found nothing by searching; I suspect we're using the wrong terminology... (Background: We are hoping to re-write the front-end web-gui in Django (current one is difficult to maintain, and hard for new developers), and as the backend (scheduler, always running) is in python and has an 'interesting'- i.e. slightly broken- db layer, we're thinking to fix to problems by taking advantage of django.) Thanks in advance, Julian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
