#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 Keywords: | Stage: Unreviewed Has_patch: 1 | ----------------------------+----------------------------------------------- loaddata command by default tries to use transaction for all it's work. But it accepts commit=False, which can made whole loaddata call part of outer transaction (this is usefull for call_command :)). But.. on any error - loaddata will close transaction in any way :(.
0. Start transaction 1. Create something in db 2. Call loaddata with commit=False (in try..except block -- we can have possible error and we know that) 3. Got an error while loaddata 4. Ooops.. loaddata rollbacks whole transaction, thus my changes in 1st step are gone 5. grrrrr. But.. loaddata for easy using in non-interactive mode should also return something "okay" to callee, right now there is no way to determine that. But this is not covered by this ticket :). p.s. not sure about component -- "Core framework" or "django-admin.py"? -- Ticket URL: <http://code.djangoproject.com/ticket/10215> 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 [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 -~----------~----~----~----~------~----~------~--~---
