I had some problems with 1.3 and Postgres 8.1, Are you using psycopg2 and pg 8.1?
On 26 September 2011 11:16, Russell Keith-Magee <russ...@keith-magee.com>wrote: > Hi Philip, > > I can't say I've seen the error you report. > > My immediate question when I see reports like this is "what else are > you doing?". Django has an extensive test suite, and things like m2m > fields are tested very heavily. Outside of Django's test suite, there > are thousands of applications out there using Django, and many of them > are using Django 1.3, and this is the first time that this particular > problem has been reported. So, you are clearly doing *something* that > is unusual (whether you know it's unusual or not). > > What we need is a reproducible test case -- the smallest possible > sample of code that works under 1.2.7, but breaks under 1.3.1. That > will provide us the basis on which to debug the problem, and form the > core of a regression test to make sure the problem doesn't occur again > in the future. > > Yours, > Russ Magee %-) > > On Mon, Sep 26, 2011 at 4:27 PM, Philip Mountifield > <pmountifi...@formac.net> wrote: > > Has anyone else experienced this error? Any help would be appreciated. > > > > Thanks > > > > Philip > > > > On 23/09/2011 14:40, Philip wrote: > >> > >> Just been updating to Django 1.3.1 and come across an odd error. I'm > >> getting the following error from some code which works with version > >> 1.2.7. > >> > >> FieldError: Cannot resolve keyword 'email_config_set' into field. > >> Choices are: id, name, site, type > >> > >> The odd thing being email_config_set is a related name for a > >> ManyToMany field. I'm not sure why django is trying to resolve it into > >> a field. > >> > >> To make it even more odd, this error occurs when DEBUG = TRUE and not > >> when DEBUG = FALSE when testing with runserver. > >> > >> I've been trying to solve this for days now with much googling/pdb/ > >> logging, but since the exception originates deep inside django I'm not > >> familiar enough to find what is going wrong: > >> > >> Traceback (most recent call last): > >> File "./core/driver.py", line 268, in run > >> self.init_norm() > >> File "./driver/emailevent/background.py", line 130, in init_norm > >> self.load_config() > >> File "./driver/emailevent/background.py", line 71, in load_config > >> events = list(config.events.select_related()) > >> File "/usr/local/lib/python2.6/site-packages/Django-1.3.1-py2.6.egg/ > >> django/db/models/manager.py", line 168, in select_related > >> return self.get_query_set().select_related(*args, **kwargs) > >> File "/usr/local/lib/python2.6/site-packages/Django-1.3.1-py2.6.egg/ > >> django/db/models/fields/related.py", line 497, in get_query_set > >> return > >> > >> > superclass.get_query_set(self).using(db)._next_is_sticky().filter(**(self.core_filters)) > >> File "/usr/local/lib/python2.6/site-packages/Django-1.3.1-py2.6.egg/ > >> django/db/models/query.py", line 550, in filter > >> return self._filter_or_exclude(False, *args, **kwargs) > >> File "/usr/local/lib/python2.6/site-packages/Django-1.3.1-py2.6.egg/ > >> django/db/models/query.py", line 568, in _filter_or_exclude > >> clone.query.add_q(Q(*args, **kwargs)) > >> File "/usr/local/lib/python2.6/site-packages/Django-1.3.1-py2.6.egg/ > >> django/db/models/sql/query.py", line 1194, in add_q > >> can_reuse=used_aliases, force_having=force_having) > >> File "/usr/local/lib/python2.6/site-packages/Django-1.3.1-py2.6.egg/ > >> django/db/models/sql/query.py", line 1069, in add_filter > >> negate=negate, process_extras=process_extras) > >> File "/usr/local/lib/python2.6/site-packages/Django-1.3.1-py2.6.egg/ > >> django/db/models/sql/query.py", line 1260, in setup_joins > >> "Choices are: %s" % (name, ", ".join(names))) > >> FieldError: Cannot resolve keyword 'email_config_set' into field. > >> Choices are: id, name, site, type > >> > >> Any ideas/solutions/pointers/tips would be most welcome. > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to django-users@googlegroups.com. > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/django-users?hl=en. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
