#22898: Specify backend name for custom SQL
-------------------------------------+-------------------------------------
Reporter: shaung | Owner: nobody
Type: New feature | Status: closed
Component: Core (Management | Version: master
commands) | Resolution: wontfix
Severity: Normal | Triage Stage:
Keywords: custom sql | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by claudep):
* status: new => closed
* resolution: => wontfix
Comment:
As you can read in the documentation, custom SQL is deprecated.
https://docs.djangoproject.com/en/dev/howto/initial-data/#providing-
initial-sql-data
The recommended path now is to use data migrations, where you should be
able to consult settings and run (SQL) code accordingly.
--
Ticket URL: <https://code.djangoproject.com/ticket/22898#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.5412e4565928bd9d9b1086499534d1e3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
