So I've had a further look into this.
Firstly, I updated to PG 8.4, and found the the issue is still there.
Secondly I had a look at Matthias' code on github and tries a few hacks.
I found that clearing the caches on the opposite side of the many to
many relationship solved the problem.
E.g.
On Mon, Sep 26, 2011 at 12:36 PM, Matthias Kestenholz wrote:
> On Mon, Sep 26, 2011 at 12:34 PM, Philip Mountifield
> wrote:
>> I also have a great deal of dynamically generated models. Interestingly in
>> my case I find the issue when using the development server with DEBUG =
>> TRUE, I've not y
On Mon, Sep 26, 2011 at 12:34 PM, Philip Mountifield
wrote:
> I also have a great deal of dynamically generated models. Interestingly in
> my case I find the issue when using the development server with DEBUG =
> TRUE, I've not yet tried it in deployment.
>
> I'll take a look at your github, thank
I actually haven't moved.. I'm still using django 1.2.x. :)
Although we plan to move to PG 9.1 and django 1.3 within the next few
weeks(we are already using both in testing)
I think i read something somewhere in the django 1.3 documentation that PG
8.1 was not supported any more(could have dreamt
I also have a great deal of dynamically generated models. Interestingly
in my case I find the issue when using the development server with DEBUG
= TRUE, I've not yet tried it in deployment.
I'll take a look at your github, thanks for sharing the link.
Out of interest, with respect to David's c
I am indeed using psycopyg2 and pg8.1, which version did you move to in
order to solve the problem? I have just been using 8.1 since it was the
default for CentOS 5, but I also see the 8.4 is available via yum.
Philip
On 26/09/2011 11:20, David Markey wrote:
I had some problems with 1.3 and P
Hi Philip
On Fri, Sep 23, 2011 at 3:40 PM, Philip wrote:
> FieldError: Cannot resolve keyword 'email_config_set' into field.
> Choices are: id, name, site, type
>
> Any ideas/solutions/pointers/tips would be most welcome.
Yes, I've seen similar problems in two sites I'm running. I suspect it
has
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 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
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
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 ke
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 nam
11 matches
Mail list logo
