0969e8edb4
We can't rely on the database returning published articles in ID order, since there are indexes on published_at and on published which could very well be in any order (btree), and no explicit `ORDER BY id ASC` was in the query. I checked the query that's run in the test against blazer, and confirmed that under real conditions the results are pretty far from ordered: ``` SELECT articles.id FROM articles WHERE (published_at <= '2021-04-27') AND articles.published = true LIMIT 10 OFFSET 0; ---- id 166916 637099 132444 431420 501939 141182 565391 515964 146231 677241 ``` Change the expectation to assert Article does not receive :order, and remove the expectation that the ids are returned in the order created. |
||
|---|---|---|
| .. | ||
| admin | ||
| articles | ||
| consumer_apps | ||
| homepage | ||