On Wed, Apr 29, 2009 at 16:03, Simon Willison <[email protected]>wrote:
> 3. (really nutty one this) - a very high scale situation where an > application is partitioned across hundreds of databases, which each > one having the same set of tables. This is how WordPress-MU works (as > used by wordpress.com), with every blog getting its own duplicate set > of tables - and it's surprisingly effective. > I would have to agree for precisely this reason. I already have a (perhaps not extremely high scale, but certainly Big Data) project using the implementation Simon described. Specifically, I have my Django-specific tables in a PostgreSQL database on one server, and then I have Django connecting to one of many MS SQL databases on two other machines, dependent on which client's data is being viewed. Obviously this took a good bit of hackery to get it working properly, and there are still a few issues buried deep within, but I did end up utilizing DSNs for determining and establishing the appropriate connections. This does, however, bring up the point of interacting with multiple database engines at once, which is not exactly configurable for a DSN. In general though I give a big +1 for DSNs. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
