> I've thought about an url like "/company1/admin" that will display me only > the "periodical" and "article" that belongs to company1.
Just be sure this is what you want. There may be times where you wish to completely separate each company's data - in which case, you can run multiple instances of Django, one for each company. In this case (at this time), this would be your quickest solution - but only if it actually fits your needs. If you have only a few companies to deal with, don't need to access all the data simultaneously, and want to start with minimal fuss, I would suggest separate projects/databases for each company. If you do, make sure you use globally-unique primary key values so you can merge databases later, if necessary. -rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users -~----------~----~----~----~------~----~------~--~---
