#18258: Too aggressive statements spliting in custom sql
-------------------------------------+-------------------------------------
Reporter: scibi | Owner: nobody
Type: Bug | Status: closed
Component: Core (Management | Version: 1.4
commands) | Resolution: wontfix
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* status: new => closed
* resolution: => wontfix
Comment:
We need a better way to run custom SQL. I don't believe there is any way
to split the SQL correctly, apart of having full parsers for each of the
different backends.
For example reliable pre_model_created, post_model_created signals could
be useful here. post_syncdb is also issued after flush which makes it
unusable.
I am going to mark this wontfix as there isn't much we can do about it.
--
Ticket URL: <https://code.djangoproject.com/ticket/18258#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
