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. for "an_instance.a_many_to_many_field" I cleared the caches in
"an_instance.a_many_to_many_field.model._meta"
Now I'm going to look into the creation of the dynamic models to see
what has changed between Django 1.2 and 1.3 in how this happens and
their sequence.
Philip
On 26/09/2011 11:37, Matthias Kestenholz wrote:
On Mon, Sep 26, 2011 at 12:36 PM, Matthias Kestenholz<m...@spinlock.ch> wrote:
On Mon, Sep 26, 2011 at 12:34 PM, Philip Mountifield
<pmountifi...@formac.net> 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, thanks for sharing the link.
Out of interest, with respect to David's comment about postgres versions, do
you use version 8.1 or another?
(Sorry for pressing send too early.)
We don't use postgresql at all (unfortunately, but that's a different
topic) on the site in question.
Matthias
--
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.
