Thursday, June 30, 2011

Re: More than one project using the same database

On Thu, Jun 30, 2011 at 4:03 PM, Cal Leeming [Simplicity Media Ltd]
<> wrote:
> The advice given to you by Andres is absolutely wrong.
> By doing this, you are opening yourself up to all sorts of race conditions.
> If you absolutely must allow this, you may want to consider implementing an
> object locking server (we have used memcache to do this before), but you'd
> need to handle this within the code logic, and you can open yourself up to
> more issues if it's not done correctly.
> Personally, I would strongly advice against doing this.
> Cal

Woah, thats a bit harsh. I can't see anything wrong with this
approach, provided that both applications use precisely the same model
definitions (preferably by sharing the app between the two projects).

In effect, it is no different from two load balanced backends talking
to the same DB server, which is *well tested*.



You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

No comments:

Post a Comment