Fix legislation process feed order #3400
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We need to add an ORDER BY clause; not doing so was causing different processes to show up sometimes. As mentioned in the PostgreSQL manual: > Because the order of the rows in the database table is unpredictable, > when you use the LIMIT clause, you should always use the ORDER BY > clause to control the order of rows. If you don’t do so, you will get > an unpredictable result set.
decabeza
approved these changes
Mar 21, 2019
voodoorai2000
approved these changes
Mar 21, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
References
Objectives
Make the legislation process shown on a feed consistent.
Notes
As mentioned in the commit message, we need to add an ORDER BY clause; not doing so was causing different processes to show up sometimes. Quoting the PostgreSQL manual: