#7800: GenericRelation doesn't respect changes from the default
GenericForeignKey
field names in the contenttypes framework
------------------------------------+---------------------------------------
Reporter: devinj | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by mtredinnick):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
The lines in the source you point to are not the problem. I think you are
misunderstanding what the `pop()` does on both those lines.
Could you construct a smaller example that demonstrates the problem? 60
lines of models to have to wade through is probably more than necessary.
And what steps have to be taken to actually trigger the issue. You're
doing something to see a particular error, but you haven't said exactly
what that is. So we can't be sure how to construct a test case that is
testing the same code paths.
It's very possible that you've found a bug, but at the moment there isn't
enough information here to repeat the problem or confirm it, so if you
could construct a small pair of models and a particular filter or query
that shows how to trigger the problem you're seeing, that would be greatly
appreciated.
--
Ticket URL: <http://code.djangoproject.com/ticket/7800#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
