#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
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* version: 2.1 => master
* severity: Release blocker => Normal
* stage: Unreviewed => Accepted
Comment:
Hello Raphael,
From what I can see this code was already broken on Django 2.0 which would
disqualify it for a backport to 2.1 since it isn't a regression.
Did you confirm it was working appropriately on Django 2.0 before
escalating it to a 2.1 release blocker?
https://github.com/django/django/commit/2a4af0ea43512370764303d35bc5309f8abce666
#diff-fe1badf69b7bc49eccc187edaa2d6d1dR146
--
Ticket URL: <https://code.djangoproject.com/ticket/29648#comment:4>
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.d552aad7b74bac815edc0bdad17c073a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
