mirror of
https://github.com/django/django.git
synced 2024-12-23 01:25:58 +00:00
Added a quick regression test that shows why Meta.ordering and order_by()
aren't always equivalent. This is documented, stable behaviour, so we should ensure it doesn't change accidentally. git-svn-id: http://code.djangoproject.com/svn/django/trunk@8312 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
942e5246ac
commit
54c313af60
@ -909,8 +909,15 @@ Traceback (most recent call last):
|
||||
...
|
||||
FieldError: Infinite loop caused by ordering.
|
||||
|
||||
# Note that this doesn't cause an infinite loop, since the default ordering on
|
||||
# the Tag model is empty (and thus defaults to using "id" for the related
|
||||
# field).
|
||||
>>> len(Tag.objects.order_by('parent'))
|
||||
5
|
||||
|
||||
# ... but you can still order in a non-recursive fashion amongst linked fields
|
||||
# (the previous test failed because the default ordering was recursive).
|
||||
>>> LoopX.objects.all().order_by('y__x__y__x__id')
|
||||
[]
|
||||
|
||||
"""
|
||||
|
Loading…
Reference in New Issue
Block a user