On Jun 23, 2006, at 2:44 PM, patrickk wrote: > another reason for splitting databases: > we have several websites sharing the same userdata (so that users > only have to register once). with every app having about 300 tables, > one database may not be the right decision. > > any ideas on how to solve this?
Well, there's no idea solution right now. A few ideas, though: - Use some form of database replication to sync the auth db across multiple databases. - Use a single-signon location view which simply sets a cookies that everything else uses to read auth info from. - Use the multi-auth branch (likely to be merged to trunk in the next few days) to write a auth util that reads from a centralized database. - Wait for multiple database support to be finished. Jacob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
