#12634: sql compiler execute: fetchone empty result with ordering_aliases fail.
---------------------------------------------------+------------------------
Reporter: [email protected] | 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 |
---------------------------------------------------+------------------------
Comment (by davidfischer):
I created a ticket in django-pyodbc's ticketing system for this:
http://code.google.com/p/django-pyodbc/issues/detail?id=79
Let's take the discussion there because it seems pretty clear that this
only affects the django-pyodbc backend and not the supported backends. I
am running into this issue as well and it is affecting me both when I
serve my app with mod_wsgi as well as `manage.py runserver`. I'll take a
more in-depth look at the problem in the next few days.
--
Ticket URL: <http://code.djangoproject.com/ticket/12634#comment:13>
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.
