On 7 syys, 00:35, Andrew Godwin <and...@aeracode.org> wrote: > That's an incredible speedup - I've had a quick look over the patch, and it > looks to be doing all the right things, so I'd definitely be behind merging > this in. Have you tried running the test runner over some third-party apps' > tests to make sure it works? I suspect South's/migrations' might get weird, > but then I do nasty things and that's my problem to fix.
I haven't ran any tests except the Django's test suite. How things should work is that if you use full_flush everything works as always, and if you don't then the only problem should be raw SQL queries (or in South's case probably also queries done through the migrations ORM). If things actually work that way is still an open question :) For raw SQL queries and other changes which aren't done through Django's ORM you can use either self.changed_models.add(some_model) or django.db.models.signals.model_changed.send(some_model) to mark that model's table as dirty. Testing this on real world apps would be really useful! - Anssi -- 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.
