pgsql: searchNotificationLayerIntroducingVulnerability order by layer ID #307
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
This fixes a bug where the API was returning Notification pages ordered by LDFV.ID instead of by Layer ID.
Quentin-M
approved these changes
Jan 19, 2017
There was a problem hiding this comment.
LGTM.
I can't recall what the ordering was based on ldfv.ID rather than ldfv.layer_id. Maybe there was an actual reason for it, or maybe it represents an actual bug. The change doesn't seem wrong to me anyways.
Let's see how it behaves both in term of performance and consistency.
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.
This fixes a bug where the API was returning Notification pages ordered
by LDFV.ID instead of by Layer ID.