#11156: Unnecessary savepoints with Oracle
--------------------------------------------------------------+-------------
Reporter: Richard Davies <richard.dav...@elastichosts.com> | Owner:
nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version:
SVN
Keywords: | Stage:
Unreviewed
Has_patch: 0 |
--------------------------------------------------------------+-------------
Savepoints are implemented in the Postgresql and Oracle backends, and
provide a useful features to users of both.
In addition, the framework itself wraps various calls in savepoints (e.g.
inside django/db/models/query.py:get_or_create). This is to work around a
Postgresql-specific oddity that the open transaction needs to be rolled
back to a prior savepoint if it experiences a database exception.
This oddity is not present on Oracle, so the extra savepoints are not
required. We probably need to split the current single backend flag
uses_savepoints into two: can_savepoint and
needs_savepoint_after_exception.
See http://groups.google.com/group/django-
developers/browse_thread/thread/bca33ecf27ff5d63
--
Ticket URL: <http://code.djangoproject.com/ticket/11156>
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
-~----------~----~----~----~------~----~------~--~---
