#11156: Unnecessary savepoints with Oracle
-------------------------------------+-------------------------------------
Reporter: Richard Davies | Owner:
<richard.davies@…> | Status: new
Type: | Version: master
Cleanup/optimization | Resolution:
Component: Database layer | Triage Stage: Accepted
(models, ORM) | Needs documentation: 0
Severity: Normal | Patch needs improvement: 0
Keywords: oracle savepoints | UI/UX: 0
Has patch: 1 |
Needs tests: 1 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by aaugustin):
To implement this, Oracle must create some sort of "implicit savepoint"
before every statement. Indeed, that means that it's never required to
create a savepoint around a single statement on Oracle.
It could be much worse, see ''Response To Errors Within A Transaction'' in
http://www.sqlite.org/lang_transaction.html :)
--
Ticket URL: <https://code.djangoproject.com/ticket/11156#comment:16>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
