#31320: Prevent BEGIN and COMMIT in RunSQL in atomic migrations.
-------------------------------------+-------------------------------------
Reporter: Adam (Chainz) | Owner: nobody
Johnson |
Type: New feature | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: new => closed
* resolution: => wontfix
Comment:
Thanks for this ticket, however `RunSQL()` is ''"useful for more advanced
features of database backends that Django doesn’t support directly"'',
moreover you can use `BEGIN` not only to start a transaction, e.g. with
[https://www.postgresql.org/docs/9.6/sql-do.html DO]. IMO parsing a custom
SQL provided by users in `RunSQL()` is out of the scope of Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/31320#comment:1>
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/068.da9f6f51d5d00423e5aa2fa2a1721a34%40djangoproject.com.
