#36152: Annotation with `%` in alias fails at db level on Postgres and MySQL
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jacob
Type: | Walls
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):
I see merit in handling the two issues separately.
#6343 refers to table and column names, which are rarely if ever driven by
user input and potentially outside the developer's control for legacy
databases (see the end of comment:4). This is a harder problem.
With this ticket's focus on aliases, which could be controlled by a user
(or a user of a reusable app, e.g. supplying dynamic annotations), I'm
seeing a consensus for deprecating the buggy behavior and a reasonable
upgrade path, since there are no database entities to adjust.
--
Ticket URL: <https://code.djangoproject.com/ticket/36152#comment:8>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701953d375e8d-0820556f-26fe-47cc-9706-9478b7bc7f54-000000%40eu-central-1.amazonses.com.
