#10215: Dont rollback transaction on errors in management/loaddata in
"non-commit"
mode.
---------------------------------------------+------------------------------
Reporter: MockSoul | Owner: nobody
Status: new | Milestone: post-1.0
Component: Core framework | Version: SVN
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Changes (by kmtracey):
* stage: Unreviewed => Design decision needed
Comment:
Note r8336 added this loaddata commit option (calling it "stealth" -- it's
not documented and not available from the command line) with an eye to
using it for implementing #8138 (speeding up tests by using transaction
rollback instead of flushing/reloading the DB). As it turns out this
loaddata option is not necessary given the way #8138 was ultimately
implemented, but I didn't actually remove it. (I meant to ask if others
thought it should be removed, but I seem to have forgotten to do that.)
Given it's not needed for #8138, at this point I don't know if it would be
better to remove it entirely or try to fix problems like this. I'm not
exactly sure how you are going to proceed after loaddata runs into a
problem but doesn't rollback -- it may have partially loaded fixtures into
the DB...you're not going to want to ultimately commit that, are you?
Personally I think it would be better to remove the option entirely since
I don't believe it was ever intended for outside use and the internal use
it was thought to be needed for got implemented in a way that made it
unnecessary. Other opinions?
--
Ticket URL: <http://code.djangoproject.com/ticket/10215#comment:3>
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
-~----------~----~----~----~------~----~------~--~---
