From 96d62b8aaa7e972da034e90acd24ebda2a844638 Mon Sep 17 00:00:00 2001
From: Henrik Levkowetz <henrik@levkowetz.com>
Date: Sun, 20 Mar 2016 17:07:36 +0000
Subject: [PATCH] Fixed a problem with paging of api lists, which requires that
the ordering keys define a fully deterministic ordering (i.e., there may be
no entries with the same sort position in order to make the api paging work).
(The admin interface's paging does not seem to have this problem.) Fixes
issue #1930. - Legacy-Id: 10957
---
ietf/meeting/models.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/ietf/meeting/models.py b/ietf/meeting/models.py
index 59f74e7d7..7d226ac02 100644
--- a/ietf/meeting/models.py
+++ b/ietf/meeting/models.py
@@ -282,7 +282,7 @@ class Meeting(models.Model):
return ts
class Meta:
- ordering = ["-date", ]
+ ordering = ["-date", "id"]
class ResourceAssociation(models.Model):
name = models.ForeignKey(RoomResourceName)
@@ -519,7 +519,7 @@ class TimeSlot(models.Model):
time__lt = self.time + self.duration + datetime.timedelta(seconds=11*60)).first()
class Meta:
- ordering = ["-time", ]
+ ordering = ["-time", "id"]
# end of TimeSlot