#27677: Disable savepoint support for MySQL NDB engine tables, and option to
overwrite the default.
-------------------------------------+-------------------------------------
Reporter: Alan Justino da | Owner: nobody
Silva |
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Alan Justino da Silva):
Replying to [comment:2 Adam Chainz]:
> I'm unsure to what lengths Django should go to support alternate
storage engines
I guess it is ok to just not disallow their use
> I'd suggest for the time making and testing a third party database
backend that overrides `uses_savepoints` (etc.), rather than changing
Django core directly right now, since we can't test it, and it doesn't
seem that popular.
Will it be better if the patch just allows the feature to be disabled,
with no explicit effort to detect the engine used? It would be enough for
now.
--
Ticket URL: <https://code.djangoproject.com/ticket/27677#comment:3>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.b70a56109d5064557e930e117ce52ec7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
