Russell Keith-Magee wrote: > It happened around mid January, as a result of the tests that use > fixtures. Every time a fixture test is executed, it flushes the > contents of the database. Flushing is a slow operation. Unfortunately, > it's also a necessary operation for those tests. > > I agree that the slowdown is less that ideal. I have a chat with > Malcolm recently about possible ways to speed things up, and we didn't > come up with any ideas that would yield any sort of significant > speedup. Any suggestions on how to improve the situation are welcome.
A wild suggestion: may be just drop an old database and create a new one? Or only create new databases during tests and drop all of them at once after? Sorry if it already works like this, I'm not familiar very much with the tests code and couldn't figure out where to look :-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
