#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                    |
-------------------------------------+-------------------------------------

Comment (by aaugustin):

 If the current implementation happens to accept strings, fantastic. But
 I'm against documenting it — because it means committing to support
 strings in these lookups forever.

 Years, months, and friends are fundamentally integers and "there should be
 one-- and preferably only one --obvious way to do it."

-- 
Ticket URL: <https://code.djangoproject.com/ticket/18969#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 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.


Reply via email to