#1919: filter truncatewords wipes newlines from string, so not chainable with
markup filters
---------------------------------+------------------------------------
Reporter: derelm | Owner:
Type: Bug | Status: new
Component: Template system | Version: master
Severity: Normal | Resolution:
Keywords: sprintsept14 | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Changes (by claudep):
* owner: nobody =>
* status: reopened => new
Comment:
I think that the parsing solution leads us nowhere. It is not fair to
penalize all backends because some cannot execute multiple statements.
IMHO, we should have a backend-specific `load_sql` that take care of
either splitting the statements or to feed the database with the read file
at once.
--
Ticket URL: <https://code.djangoproject.com/ticket/1919#comment:23>
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 https://groups.google.com/groups/opt_out.
