#1796: [patch] "Cannot resolve keyword ___ into field" error when working with
ManyToMany relation
-------------------------+--------------------------------------------------
Reporter: anonymous | Owner: mtredinnick
Status: reopened | Component: Database wrapper
Version: SVN | Resolution:
Keywords: | Stage: Accepted
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------+--------------------------------------------------
Changes (by anonymous):
* stage: Ready for checkin => Accepted
Comment:
I'm going to apply this patch, but purely as a temporary workaround. It
won't close the ticket, since the patch doesn't fix the problem; it just
hides it. We are wall-papering over the real problem here: why isn't the
app cache being initialised properly in the case under consideration? If
we see the problem in one scenario, who's to say we don't have it occuring
elsewhere.
Since the app-cache and model loading code is in the queue for
refactoring/redesign in any case, I don't feel to bad about applying a
temporary workaround like this. But I'm going to leave the ticket open
(and assigned to me).
--
Ticket URL: <http://code.djangoproject.com/ticket/1796#comment:44>
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
-~----------~----~----~----~------~----~------~--~---
