#17952: Sqlite and mysql generating different queries with the same code
-------------------------------------+-------------------------------------
Reporter: glen.nelson.1@… | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.3
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: | Triage Stage:
Has patch: 0 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* status: new => closed
* resolution: => worksforme
Comment:
I tested this with a trivial test in regressiontests/aggregation_regress:
{{{
def test_range_filtering(self):
start = datetime.datetime(1900, 1, 1)
end = datetime.datetime(2100, 1, 1)
qs = Book.objects.filter(pubdate__range=(start, end)).values(
'contact').annotate(Count('id')).order_by()
print qs
print qs.query
}}}
I could not reproduce the reported error in HEAD. It might be I am missing
some key piece of the puzzle. That piece should be provided by the
original reporter. Closing as worksforme, please reopen with additional
information about the used models if the error is still present for you in
1.4 or HEAD.
--
Ticket URL: <https://code.djangoproject.com/ticket/17952#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.
