#9596: Comparing a DateTimeField to a date is too hard
---------------------------------------------------+------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: new | Milestone: post-1.0
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
lookup_type date datetimefield compare comparison query_term field lookup
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 1 |
---------------------------------------------------+------------------------
Changes (by Scott <[EMAIL PROTECTED]>):
* needs_better_patch: 0 => 1
* version: 1.0 => SVN
* needs_tests: 0 => 1
* milestone: => post-1.0
Comment:
Patch B is an implementation which adds code to all the backends. It works
by truncating the date a la "DATE(datetimefield)", like the first patch.
The downside is that the datetime column must be truncated, which adds a
large overhead to the query especially if the column is indexed.
--
Ticket URL: <http://code.djangoproject.com/ticket/9596#comment:3>
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
