#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 russellm):
Michael:
I stand corrected on TRUNCATE in 7.x. I had a quick look and couldn't find
it, but I'll admit that I didn't look that hard once I knew that TRUNCATE
in 8.0 wasn't going to work. Thanks for the pointer.
The reason I went with TRUNCATE over DELETE is speed. Fixtures need to be
added and removed for every test case in the system, so the fixture
installation process needs to be as fast as possible. I initially started
with a 'drop constraints and DELETE' approach, but then I remembered the
speed advantage in TRUNCATE.
The removal of constraints is a little messy because an implied constraint
is created whenever a REFERENCES to a previous table is added, and its a
little nasty to find the name of these implied constraints. I'm currently
playing with another approach based around putting DEFERRED/DEFERRABLE in
the table definitions; I'll let you know how I go.
--
Ticket URL: <http://code.djangoproject.com/ticket/2333#comment:37>
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
-~----------~----~----~----~------~----~------~--~---
