Closed tangrammer closed 3 years ago
Closing this issue after ensuring that the different ordering in aggregation results was related to different implementation in new postgres image (google cloud version) https://github.com/akvo/akvo-lumen/commit/6d7e35c4f01898a4405440b6766e13e5b89df508
Context
This commit was necessary to have tests running again https://github.com/akvo/akvo-lumen/commit/e9be8412eeebeda58ade4fc5a0033f96f8725872
Ensure that aggregation shouldn't be affected and this ordering response doesn't affect vizs
Problem or idea
What is the cause?
Solution or next step
How could we solve it?