#30494: Problem with ExtractYear()+1 in queries
-------------------------------------+-------------------------------------
Reporter: Alexey Chernov | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"4d1420947e79bc89d266229feea305294ec896ee" 4d142094]:
{{{
#!CommitTicketReference repository=""
revision="4d1420947e79bc89d266229feea305294ec896ee"
Fixed #30494 -- Disabled __year lookup optimization for indirect values.
The previous heuristics were naively enabling the BETWEEN optimization on
successful cast of the first rhs SQL params to an integer while it was
not appropriate for a lot of database resolved expressions.
Thanks Alexey Chernov for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30494#comment:4>
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/070.fdb03beace7148fecdcf462a05b323e1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
