#23426: migrations.RunSQL's function signature implies it won't do any parameter
substitution
-------------------------------------+-------------------------------------
Reporter: ris | Owner:
Type: | Markush2010
Cleanup/optimization | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: migrations sql | Triage Stage: Accepted
runsql params escape | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by loic):
I wouldn't allow 2 as it doesn't bring much to the table, only:
- "SQL 1; SQL 2; ..." used for backwards compat and to allow reading SQL
from a file.
- ["SQL 1", "SQL 2", ...] used to build a sequence programatically.
- [("SQL 1", params), ("SQL 2", params), ...] used to pass params to
statements.
--
Ticket URL: <https://code.djangoproject.com/ticket/23426#comment:12>
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/061.5660391fc5ddc8ec320ae73fa0a117d2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
