#10071: month and day lookup arguments should be integers
---------------------------+------------------------------------------------
 Reporter:  leosoto        |       Owner:  nobody    
   Status:  new            |   Milestone:            
Component:  Uncategorized  |     Version:  1.0       
 Keywords:  jython         |       Stage:  Unreviewed
Has_patch:  1              |  
---------------------------+------------------------------------------------
 On [8131] we forgot to normalize month and day lookups to be passed as a
 consistent type to the backend. Later, on [8494] and [8526] they were
 normalized as unicode, apparently to avoid problems with SQLite.

 This is a problem for backends which are strict in terms of the argument
 data types. Specifically, on PostgreSQL and JDBC, it doesn't work if you
 compare the year of a date column against an string. Also, I don't see how
 to fix the problem on the backend layer, as it doesn't seem to have a
 chance to do the needed type conversion.

 Now, considering than months and day numbers are, well, numbers, int
 sounds like a better type than unicode for interfacing with the backend.
 The attached patch does this change, without breaking the sqlite3 backend.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/10071>
Django <http://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