Inconsistent results when paginating

[charltongroves]

Ran into a very puzzling issue when using .page

Plucking specific columns (eg, SELECT "organisations"."id" FROM "organisations") using pagination leads to a different set of data than loading the whole record (eg, SELECT "organisations".* FROM "organisations").

This is very bad as demonstrated by the use case

orgs = Organisation.page(1).per(20)
...
org_ids = Organisation.page(1).per(20).pluck(:id)

As a developer you would expect the results of those to be consistent, but they lead to completely different data as shown in the screenshot.

Enforcing a .order(:id) fixes the issue, but since your gem shows many use cases without using order it should be assumed that you dont have to use order to get consistent results.

[charltongroves]

I think i found the issue

When using limit/offset without an order_by you get indeterminate results depending on the how SQL optimises the query in the query plan

I would suggest updating your docs to encourage people to use order at all times when using .page