#9358: .dates(...) only spitting out a single date, bug in queryset order
---------------------------------------------------+------------------------
Reporter: dokterbob | Owner: nobody
Status: new | Milestone: post-1.0
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords: dates
order .dates sqlite
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by mtredinnick):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
"Order by 1" is perfectly valid SQL and not at all mysterious. We need
some more details here to work out if it's a bug in a particular version
of SQLite or in SQLite in general and what a reasonable way to work around
it will be. Ordering by event_date, as you suggest is not, from memory,
going to be valid SQL, since all columns that appear in an ordering
statement must appear as output columns in the select statement (and we're
not selecting event_date, but something derived from event_date, so it's
an input column and not an output column).
What version of SQLite are you using? On what platform?
--
Ticket URL: <http://code.djangoproject.com/ticket/9358#comment:1>
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 [email protected]
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
-~----------~----~----~----~------~----~------~--~---
