#11156: Unnecessary savepoints with Oracle
-------------------------------------+-------------------------------------
Reporter: Richard Davies | Owner: (none)
<richard.davies@…> |
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: oracle savepoints | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => wontfix
Comment:
I'm going to wont-fix this one.
No conversation update for the past 9 years and still no performance
benchmarks demonstrating that it is a change worth the extra complexity it
introduces.
The transaction logic is already complex and Oracle has proven to be the
hardest backend to support for the past years. I'm far from convinced than
attempting to take advantage of this
[https://docs.oracle.com/cd/E11882_01/server.112/e40540/transact.htm#CNCPT1115
statement-level atomicity feature] will bring more benefits than the
maintenance burden it will incur.
--
Ticket URL: <https://code.djangoproject.com/ticket/11156#comment:17>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701829a31221d-a57b3571-d02b-4509-ab16-d80b5c915524-000000%40eu-central-1.amazonses.com.
