#31271: Logged queries may interpolate parameters in the wrong order on Oracle.
-------------------------------------+-------------------------------------
Reporter: Hans Aarne Liblik | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: oracle sql log | Triage Stage: Accepted
debug logging |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* component: Uncategorized => Database layer (models, ORM)
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
Comment:
Thanks for this report. `last_execute_query()` didn't interpolate
parameters before 79065b55a70cd220820a260a1c54851b7be0615a, so we can
treat this as a regression. It seems that the only reasonable solution is
to use mechanism that preserves ordering in `_fix_for_params()`, but it
can be tricky to add a regression test. I was not able to reproduce an
incorrect behavior but I agree that this can happen.
Would you like to prepare a patch?
--
Ticket URL: <https://code.djangoproject.com/ticket/31271#comment:1>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/073.87da64dbc2d4d40e8ddaaf3446a6c404%40djangoproject.com.
