#29648: Incorrect escaping when using subqueries inside datetime truncation
functions
-------------------------------------+-------------------------------------
Reporter: Raphael Michel | Owner: Raphael
| Michel
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: Subqueries Datetime | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Raphael Michel):
Sorry, no, you're correct, it was broken in 2.0 already.
Does that mean we can't have the fix in 2.1.1, but will need to wait for
2.2? That would be very unfortunate, since there's no workaround, and
we'd need to run a custom patched version of Django in production for more
than 6 months :(
--
Ticket URL: <https://code.djangoproject.com/ticket/29648#comment:5>
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/066.576f9351c807eb5fb07b22f6399490f1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
