#4146: Database Module Conflicts
------------------------------------------------+---------------------------
Reporter: David Cramer <[EMAIL PROTECTED]> | Owner: adrian
Status: closed | Component:
Database wrapper
Version: SVN | Resolution:
invalid
Keywords: | Stage:
Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------------------+---------------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => invalid
Comment:
I think I see what you are talking about now (and yes, surprisingly enough
I '''did''' read the paste fragment before posting my request for
clarification). It wasn't clear until you explained it that that fragment
was actually two or three different files.
This is no bug here.
The {{{cursesite.portals.wow.profiles.models.Equipment}}} model is
''explicitly'' referring to the Item class it imported -- from
{{{cursesite.portals.wow.profiles.models}}}. If you want to refer to the
other Item class, you should import that instead. Since you are referring
to things by reference, there is no ambiguity possible and no reason to
check INSTALLED_APPS (which we don't do). In fact, this is necessary
behaviour because otherwise you wouldn't be able to create foreign keys to
both Item classes from the same model (which you can do at the moment by
importing both of them and referring to them by reference).
--
Ticket URL: <http://code.djangoproject.com/ticket/4146#comment:8>
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
-~----------~----~----~----~------~----~------~--~---
