On May 17, 2011, at 7:16 AM, Jonas H. wrote: > 3) Hash the SQL generated for setup/fixtures. (step in right before the SQL > is sent to the database) > Advantages: No false-positives, simple > Disadvantages: Does not eliminate the need for SQL generation and fixture > parsing + model creation, so this might not be the "highest of highs" ;-)
FWIW, I tried this awhile back while trying to get rid of the necessity of the FORCE_DB option in test-utils (https://github.com/jbalogh/test-utils/blob/master/test_utils). It added 2 seconds to our test startup time, so I decided against it. It wasn't clear from the profiles that string manips (SQL generation) was taking a lot of that time, so I decided to forgo the model metadata deep comparison code I had thought about writing. -- 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.
