#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 ikelly):
It's a bit weird, I agree. The Oracle docs refer to this as "statement-
level atomicity":
[http://docs.oracle.com/cd/E11882_01/server.112/e10713/transact.htm]
Transactions are guaranteed to be atomic (e.g. in case of system failure),
but an unsuccessful statement is not considered part of the transaction.
--
Ticket URL: <https://code.djangoproject.com/ticket/11156#comment:15>
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.
