#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
-------------------------+--------------------------------------------------
Comment (by mtredinnick):
Øyvind: It's typically been somewhat dependent on a number of things
including hardware (different CPUs give different results; this I know
from previous experience), OS, Python micro version and installed apps. A
simple example would be nice, but it might also be difficult to construct.
One request for everybody posting here: We really don't need any more "it
happens for me, too" comments. They adds no value and make it hard to
separate the useful comments out. We know it happens. We even understand
mostly why. I'll get back to looking at this pretty soon (within the week,
most likely), since I'll have a block of time to focus on it. So if
everybody can be patient for a little longer (and hold off on the "me,
too!" posts, since it's sounding a bit too much like AOL here) we'll get
it fixed as soon as we can.
--
Ticket URL: <http://code.djangoproject.com/ticket/1796#comment:65>
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
-~----------~----~----~----~------~----~------~--~---
