#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
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"2a038521c4eabdc5f6d5026d3dd6d22868e329cd" 2a038521]:
 {{{
 #!CommitTicketReference repository=""
 revision="2a038521c4eabdc5f6d5026d3dd6d22868e329cd"
 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.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31271#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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.0c14b9bb9510a0f949d9e52d5aa18117%40djangoproject.com.

Reply via email to