Defect #29581

Issues in paginated views may be lost because sorting criteria are not unique

Added by Mizuki ISHIKAWA about 1 month ago. Updated 15 days ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues list
Target version:4.1.0
Resolution: Affected version:

Description

This is a problem that the issue that should be present is not displayed on the issues/index.
The same problem may exist even at index other than issues/index.

This problem occurs when using PostgreSQL.
If you use only non-unique fields such as trackers or categories as the sorting criteria, there is a possibility that some issues will not be displayed on pagination views.

This phenomenon is described in the document of PostgreSQL. (As a specification rather than a bug)
https://www.postgresql.org/docs/8.3/static/queries-limit.html

Questions about the same problem:
https://stackoverflow.com/questions/13580826/postgresql-repeating-rows-from-limit-offset

I attached file is the test I wrote to reproduce this problem.
If you are using PostgreSQL, that test will fail. ( Non-paginated issue ids and paginated issue ids should be the same. )

Failure:
--- expected
+++ actual
@@ -1 +1 @@
-[2, 12, 11, 8, 7, 5, 3, 1, 13]    # Non-paginated issue ids
+[11, 12, 12, 7, 7, 5, 3, 1, 13]  # Paginated issue ids

add-test-that-fails-when-using-postgresql.patch Magnifier (877 Bytes) Mizuki ISHIKAWA, 2018-09-10 07:35

fix-29581.patch Magnifier (3.36 KB) Mizuki ISHIKAWA, 2018-09-20 10:21

History

#1 Updated by Mizuki ISHIKAWA 26 days ago

I wrote a patch to solve this problem.

I fixed to add unique fields (ex: issues.id, time_entries.id) as sort criteria.

#2 Updated by Go MAEDA 15 days ago

  • Target version set to 4.1.0

Setting target version to 4.1.0.

Also available in: Atom PDF