#18969: ORM filtering with "year" lookup for dates
-------------------------------------+-------------------------------------
Reporter: saippuakauppias | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by fhahn):
* cc: flo@… (added)
Comment:
This issue seems fixed already, your test case works for me on sqlite and
postgres using the current master, the sql is generated correctly.
I'm not sure about the position of the test date generation, but you could
create an article with {{{ datetime.datetime(1, 3, 3) }}} and it wouldn't
mess with the previous assertions.
Could you upload a patch with the test case only? Or even better, create a
pull request on github?
This ticket describes a bug similar to #18176
--
Ticket URL: <https://code.djangoproject.com/ticket/18969#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
