#18176: SQL queries for filtering datetime objects use incorrect format for 
years
<1000
-------------------------------------+-------------------------------------
     Reporter:  rrotaru              |                    Owner:  rrotaru
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  1.4
  (models, ORM)                      |               Resolution:
     Severity:  Normal               |             Triage Stage:  Accepted
     Keywords:  datetime, SQL, year  |      Needs documentation:  0
    Has patch:  0                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by rrotaru):

 It turns out that python interprets numbers with leading zeroes as octal
 input (hence why anything with a leading zero that also contains an 8 or 9
 causes an invalid token error). It seems like allowing strings to be
 passed in year lookups would solve both issues and might be the most
 reasonable approach.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/18176#comment:2>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to