#2333: Add unit test framework for end-user Django applications
---------------------------------+------------------------------------------
Reporter: russellm | Owner: russellm
Status: new | Component: Unit test system
Version: SVN | Resolution:
Keywords: unit test doctest | Stage: Design decision needed
Has_patch: 1 | Needs_docs: 1
Needs_tests: 0 | Needs_better_patch: 1
---------------------------------+------------------------------------------
Comment (by Michael Radziej <[EMAIL PROTECTED]>):
DEFERRED with DELETE work, but TRUNCATE automatically gets its own
transaction, so it doesn't work.
Inserts are *much* faster without foreign key constraints. But most of the
time you don't insert a lot of data, or do you?
I'd simply try to use TRUNCATE, and fall back to completely drop all
tables and resync if TRUNCATE fails. With a bit of luck, people will
improve this for their favourite database and provide patches ;-)
Isn't that a problem with mysql, too? #2720 describes a bug that means
that mysql foreign key constraints are created in the wrong way ...
--
Ticket URL: <http://code.djangoproject.com/ticket/2333#comment:38>
Django Code <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 [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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
