#9205: Add savepoint protection to Model.save()
-----------------------------------------------------------------------+----
Reporter: Richard Davies <[EMAIL PROTECTED]> | Owner:
nobody
Status: new |
Milestone:
Component: Database layer (models, ORM) |
Version: SVN
Resolution: |
Keywords:
Stage: Design decision needed |
Has_patch: 1
Needs_docs: 0 |
Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------------------------------+----
Changes (by mtredinnick):
* needs_better_patch: => 0
* stage: Unreviewed => Design decision needed
* needs_tests: => 0
* needs_docs: => 0
Comment:
Django should not be in the business of deciding how users wish to handle
database-level errors. That is why saving doesn't do this right now. This
is essentially a disguised version of what you were asking for in #8739,
by the way. It is up to the caller to decide whether they want to roll
things back entirely, or go back to an earlier savepoint they set or what.
At the moment, I don't think this change should go in, but I want to think
about what we can do to possibly make some things easier. The current
behaviour feels the most natural to me for now, since there definitely
isn't a one-size fits all and the extra database interaction overhead
isn't something we should impose on everybody.
--
Ticket URL: <http://code.djangoproject.com/ticket/9205#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
