#31271: Logged queries may interpolate parameters in the wrong order on Oracle.
-------------------------------------+-------------------------------------
Reporter: Hans Aarne Liblik | Owner: felixxm
Type: Bug | Status: closed
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: oracle sql log | Triage Stage: Accepted
debug logging |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"2448b3182c75cce5d22dd80be0fb5cba6104c364" 2448b31]:
{{{
#!CommitTicketReference repository=""
revision="2448b3182c75cce5d22dd80be0fb5cba6104c364"
[3.0.x] Fixed #31271 -- Preserved ordering when unifying query parameters
on Oracle.
This caused misplacing parameters in logged SQL queries.
Regression in 79065b55a70cd220820a260a1c54851b7be0615a.
Thanks Hans Aarne Liblik for the report.
Backport of 2a038521c4eabdc5f6d5026d3dd6d22868e329cd from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31271#comment:7>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.deb62bc1a85411e61c9d501b227f2a19%40djangoproject.com.
