#12634: sql compiler execute: fetchone empty result with ordering_aliases fail.
---------------------------------------------------+------------------------
Reporter: v...@163.com | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: 1.2-beta
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by russellm):
* status: reopened => closed
* resolution: => invalid
* milestone: 1.2 =>
Comment:
Again, this isn't a problem that exists for any of the officially
supported backends. I strongly suspect that it's a problem with
django_pyodbc. On IRC, Ramiro (The Django PyODBC author) agreed that this
was likely.
Closing until someone can demonstrate that this is actually a problem with
Django itself.
--
Ticket URL: <http://code.djangoproject.com/ticket/12634#comment:11>
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-upda...@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.
