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?
Phil
On 26/09/2011 11:27, Matthias Kestenholz wrote:
Hi Philip
On Fri, Sep 23, 2011 at 3:40 PM, Philip<pmountifi...@formac.net> 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 to do with dynamically created models and startup timing effects
in our case. I'm not sure when it started and it's really hard to test
because it only happens in production (mod_wsgi / DEBUG=False) and I
don't have a consistent view of when the problem happens yet.
What we are doing in FeinCMS against it is trying to remove the caches
on Model._meta when new models are being created; this works for us,
but isn't all that nice. I'm running the following code in production
and will be waiting a few hours / days for the problem to manifest
itself again, hoping it wont:
https://github.com/matthiask/feincms/commit/f2de708a09f8b6cf4fdbca6b3583747b6ebbc2e2
Matthias
--
Philip Mountifield
Formac Electronics Ltd
tel +44 (0) 1225 837333
fax +44 (0) 1225 430995
pmountifi...@formac.net
www.formac.net
www.telgas.net
--
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.
