#9006: QuerySet indexing by __getitem__ gets wrong answer in edge cases
-------------------------------------+--------------------------------------
Reporter: smoluf | Owner: mtredinnick
Status: assigned | Milestone:
Component: Core framework | Version: 1.0
Resolution: | Keywords: queryset index race
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Comment (by john):
This may just be due to the fact that LIMIT queries without ORDER BY
aren't guaranteed to return consistent result sets. The problem may be
specific to PostgreSQL (see http://www.postgresql.org/docs/8.3/interactive
/queries-limit.html); I haven't had time to research the other supported
databases.
This patch doesn't break anything, according to runtests, and it solved
the problem I was having in the admin interface (see #9076).
--
Ticket URL: <http://code.djangoproject.com/ticket/9006#comment:5>
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-updates@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
