#27498: Filtering annotated field in SQLite returns wrong results
-------------------------------------+-------------------------------------
Reporter: Tim Düllmann | Owner: Peter
| Inglesby
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: sqlite, | Triage Stage: Accepted
annotations, filter |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Aymeric Augustin):
Regarding bug one, we could use the same approach as #14091 for SQLite.
It's annoying to have to do this in Django. But if we're concerned about
people feeding these incorrectly generated and thus insecure queries to
databases, then the logical conclusion is to escape parameters in Django
before substituting them. This won't make the problem worse.
This ticket is really about bug two. Let's focus on that one here.
--
Ticket URL: <https://code.djangoproject.com/ticket/27498#comment:6>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.f5f40147aac0dcb904f8f4cf920ac35e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
