On Tue, May 17, 2011 at 9:16 AM, Jonas H. <[email protected]> wrote: .... > Invalidation is what I'm unsure about too -- multiple ideas came to my mind, > all involving some sort of Great Hash(tm):
Even within a single test command run, the same DB setup and same fixture loads are done many times (for a sizable suite). Invalidating too often is better than invalidating too little. > 1) Use file modification timestamps for all model and test related files. > Advantages: simple, works. > Disadvantages: Triggers cache invalidation for changes not related to models > or tests I think this is a pretty big win, even though it's not theoretically optimal. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
