#12634: sql compiler execute: fetchone empty result with ordering_aliases fail.
---------------------------------------------------+------------------------
Reporter: [email protected] | Owner: nobody
Status: closed | Milestone: 1.2
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
Comment:
Again, closing invalid. Unless you can provide a query that invokes this
line of code *and* demonstrate that isn't caused by a flaw in either the
PyODBC DBAPI or the django_pyodbc stack, this isn't a flaw in Django.
Regarding the first part of this requirement: "Access /admin" isn't a
reproduction instruction for an ORM flaw.
Regarding the second part: Looking at the proposed patch, I'm inclined to
suggest that the problem lies with django_pyodbc using ordering aliases
when it shouldn't. If you can narrow down a specific query and show that
django_pyodbc *requires* an ordering alias that isn't required by other
backends, I'll accept that as Django's problem.
--
Ticket URL: <http://code.djangoproject.com/ticket/12634#comment:8>
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.
