#4146: Database Module Conflicts
------------------------------------------------+---------------------------
Reporter: David Cramer <[EMAIL PROTECTED]> | Owner: adrian
Status: reopened | Component:
Database wrapper
Version: SVN | Resolution:
Keywords: | Stage:
Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------------------+---------------------------
Comment (by mtredinnick):
David, even if this used to work, it was purely by accident and it's not
something you should rely on.
If you are wanting Django's ORM to work with an application, it should be
in the INSTALLED_APPS list. That isn't an unreasonable requirement and
it's what saves you from having to annotate both end of relation fields,
for example. As I mentioned above, there is a lot of code that relies on
using the app_cache to work between models and it would be quite a
restriction on future development if we also needed to make sure things
worked for the very rare cases where something isn't in INSTALLED_APPS
(some things won't work at all, even now, for apps not in that list).
So this ticket is only a bug if it continues to occur when both apps are
in the installed list.
--
Ticket URL: <http://code.djangoproject.com/ticket/4146#comment:12>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
