Files
gitlabhq/spec/models
Sean McGivern d7a5a28c53 Fix pagination on sorts with lots of ties
Postgres and MySQL don't guarantee that pagination with `LIMIT` and
`OFFSET` will work if the ordering isn't unique. From the Postgres docs:

> When using `LIMIT`, it is important to use an `ORDER BY` clause that
> constrains the result rows into a unique order. Otherwise you will get
> an unpredictable subset of the query's rows

Before:

    [1] pry(main)> issues = 1.upto(Issue.count).map { |i| Issue.sort('priority').page(i).per(1).map(&:id) }.flatten
    [2] pry(main)> issues.count
    => 81
    [3] pry(main)> issues.uniq.count
    => 42

After:

    [1] pry(main)> issues = 1.upto(Issue.count).map { |i| Issue.sort('priority').page(i).per(1).map(&:id) }.flatten
    [2] pry(main)> issues.count
    => 81
    [3] pry(main)> issues.uniq.count
    => 81
2016-06-23 15:26:50 +01:00
..
2016-06-20 16:52:05 +08:00
2016-06-18 05:46:45 +02:00
2016-06-01 16:22:35 +02:00
2016-06-01 12:10:08 +02:00
2016-05-29 15:03:00 -04:00
2016-06-18 05:46:45 +02:00
2016-05-16 18:03:55 -05:00
2016-03-20 22:55:08 +01:00
2016-06-01 16:22:35 +02:00