In theory, unless you've disabled transactions, the database should be able to manage all contention issues. Enviado desde mi BlackBerry de Movistar (http://www.movistar.com.ar)
-----Original Message----- From: ALJ <astley.lejas...@gmail.com> Sender: django-users@googlegroups.com Date: Thu, 30 Jun 2011 04:46:15 To: Django users<django-users@googlegroups.com> Reply-To: django-users@googlegroups.com Subject: More than one project using the same database I have an extranet type project that has been running for a year. It only has a maximum user base of about 50 people of which probably only a few are using it at any one time. The users can add, edit and delete items within the application However, we need to expose the data in that extranet application to a another group of users but through another domain. Anonymous users will be able to register requests to be contacted, and another group of known users will be able to log in with read only access to see the status of those requests. My question is, what are the issues that I need to think about (are race issues one?), is it possible to detect if these issues could occur in my particular situation, and how do you mitigate against these. ALJ -- 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. -- 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.
