On Thu, 2009-04-30 at 11:33 -0700, eric.frederich wrote: > Malcom, > > That helped. > > I think I understand what you're saying. > > I could have two projects, projectA that has appA1 and appA2 installed > and projectB that has appB1 and appB2 installed. > If projectA and projectB's settings.py file shares the same DB > info...then projectB would be able to use data from appA1 just by > importing the models from appA1. > Would projectB need to list appA1 in INSTALLED_APPS or in a projectB > view could I just do "from appA1.models import SomeModel"?
You should definitely put appA1 in the INSTALLED_APPS list for projectB. There are some very limited cases where you could get away without doing that, but it would be very fiddly to debug when things go wrong and there's pretty much no gain at all in not doing so. > So it seems pretty easy and straightforward if the apps either exist > in the same Django project or utilize the same database. Of course, > the former would imply the latter. Right. The data isn't tied to projects, it's tied to the database and the (reusable) apps are used to access the data (and provide the model definitions) in more than one installation at the same time. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
