> > On the other hand, if the two websites are entirely independent, putting > > them into a single database is simply poor design. It's trivial to > > create a separate database and why not use the tools that are available > > instead of adding extra complexity?! > > I think the idea is to allow common authorisation between the two sites.
I am a complete newbie here, so pardon me chipping in, but... would it not be possible to do authorisation in one database and then have the groups-specific databases being separate? Derek --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
