#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 |
---------------------------------------------------+------------------------
Comment (by kmtracey):
Note given the posted stack trace, it's not any of the app's queries that
is triggering this. It is the session middleware calling
request.session.save(), which is ultimately calling exists()...so it's the
query that is generated by an exists() call, which is internal to the ORM
and not something the app can influence.
--
Ticket URL: <http://code.djangoproject.com/ticket/12634#comment:9>
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.
