#8792: Django's unit test system wipes out "custom sql" data before performing
tests
----------------------------------------+-----------------------------------
Reporter: deltoide | Owner: nobody
Status: closed | Milestone:
Component: Testing framework | Version: SVN
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Comment (by kmtracey):
Replying to [comment:5 jacob]:
> In 1.1 unit tests no longer flush, but instead use a transaction. So
this is no longer valid.
Hmm, well flush is still used on MySQL/MyISAM since it doesn't support
transactions. But hooking into the post_syncdb signal seems like a viable
solution for the case where tests still flush the DB, so leaving closed.
--
Ticket URL: <http://code.djangoproject.com/ticket/8792#comment:6>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
