#11900: commit_on_success: Handle Exception in commit()
---------------------------------------------------+------------------------
Reporter: guettli | Owner:
gabrielhurley
Status: assigned | Milestone: 1.2
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by gabrielhurley):
* needs_tests: 1 => 0
Comment:
This specific bug seems to be backend-specific (it seems to be completely
impossible to trigger it using SQLite3). I did manage to duplicate it,
test it, and patch it using a server running psycopg2. The general
principle of the fix seems universally applicable, though.
The patch I added has both the requested test and an updated version of
the original patch that works with the new MultiDB in 1.2. Hopefully it's
good to go now.
--
Ticket URL: <http://code.djangoproject.com/ticket/11900#comment:5>
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.
