#30445: RunSQL Migration should accept psycogp2 sql.Composable object.
-------------------------------------+-------------------------------------
Reporter: suomenusko | Owner: nobody
Type: New feature | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: wontfix
Keywords: RunSQL | Triage Stage:
sql.Composable | 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
* version: 2.2 => master
* resolution: => wontfix
Comment:
Thanks for the report, however this is
[https://docs.djangoproject.com/en/stable/ref/migration-operations/#runsql
documented] behavior:
> sql, and reverse_sql if provided, should be strings of SQL to run on the
database. On most database backends (all but PostgreSQL), ...
I don't think that we should add any complexity here. If you want to use
`psycopg2.sql.Composable` you can always do this via `RunPython()`.
--
Ticket URL: <https://code.djangoproject.com/ticket/30445#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 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/068.62df66c9e62f84bf58dd268d6eaaf91e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
