Alright, I've now removed my AppCache state handling and replaced it with swappable AppCaches - surprisingly, doing this hasn't broken anything, but it did need an AppCacheWrapper to stop references going wrong.
The commits are here: https://github.com/andrewgodwin/django/commit/dbc17d035b255a4da977251fe399f5c80cffeecd https://github.com/andrewgodwin/django/commit/49d1e6b0e20a363cbf9b105e8e6d3fc5fc1cad2f The SQLite test suite all passes after these changes, so this is looking good. Thoughts? Andrew On Tue, Sep 18, 2012 at 4:49 PM, Andrew Godwin <and...@aeracode.org> wrote: > An update from discussions with Alex and Anssi - I'm going to modify > things a little so we don't have a Borg-pattern AppCache (i.e. you can > instantiate it multiple times and get different caches), which should solve > most of the problems currently caused by app cache state fiddling. Should > take a day or two. > > I can help with Oracle problems if you encounter a such thing since that's >> my main backend I work with. (And I have to deal with all the pain it >> causes) > > > Thanks Jani - that would be much appreciated. It should be possible to get > a decent way just from the Oracle module, I'll let you know when I get > around to it. > > Andrew > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
