Hi List, Maybe someone can hint me in the right direction with this.
Im using Django backed by a non relational database, declaring my django models is enough in order to store and retrieve data, so I devised a design where models itself are declared by instantiating the metaclasses and using type() based on entries stored in Model and associated Field entities in said database. This is all working as expected, across different threads and instances even, except for the admin-app, I have to restart the instances in order for changes to the model to become visible there, even though everywhere else the changes are instantly and consistently visible. Is there perhaps another method of caching models being employed by the admin-site besides the model cache in db.models.loader? I'm already updating the model cache the moment a model/field record fires one of the related signals. Regard, Yuka -- 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.
