On Thu, Aug 28, 2008 at 8:18 PM, Rock <[EMAIL PROTECTED]> wrote: > > What you are describing is an edge case for the notion of "sharding" > which is the deployment of identically structured DBs where different > batches of users get saved in different databases. (Flickr does this.)
You could also move the sharding from the application to the db. MySQL has MySQL Proxy <http://forge.mysql.com/wiki/MySQL_Proxy> which HSCALE <http://hscale.org/display/HSCALE/Home> uses. Not sure about other DBs. This way Django would just keep working as is. Ben. -- www.playfire.com - now in public beta! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
