Mmm... it's a bit confusing. If I get you, you have 2 projects. Project1 has 2 apps that you would like to reuse in Project 2.
And you have 2 different DB, one for each. And you are wondering how the projects will differenciate them? There is right now a thread about project and application differenciation (project organization and decoupling) that might interest you. Anyway, each project has it's own database that is defined in settings.py, and thus there should not be any mixing of databases. Another thing would be if you wanted to reuse the same database, and in that case you might want to extend the User model to add a site field that would keep the site the user inscribed to. Hope it helps. G On 1/17/07, ZebZiggle <[EMAIL PROTECTED]> wrote:
Anyone? ZebZiggle wrote: > Hey all, > > Belated Happy New Year! > > I'm embarking on a new Django project (a business application vs. the > http://www.MyDarkSecret.com game of my previous effort). I'm hoping to > use the admin capabilities of Django for this project. > > However, I have App A and App B both installed in the same Project as > separate applications, but I've got some conflicting privileges (and > some that conflict with the default admin privileges). For example, I > already have a Users table and a Messages table in Project A and I'm > about to introduce another User table in Project B. > > Is there a way to differentiate these? Or is the only option to make a > new Project? > > If this isn't clear ... let me know and I'll elaborate. > > Keep up the great work everyone! Django is killer. > > -Sandy >
--~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
