Conversation
Contributor
Author
|
This should be ready for review. If configured, the order is specified for all sort fields including the sort id field (which never should be I tested it with the "vineyards" API, by adding the option and by adding "village_info" to the sortables. |
This file contains hidden or 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
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 change adds a query generation option
nullOrderto SQL feature providers to control the sort order for columns with null values. If no value is provided, the default order of the database applies. Forlast, the rows withnullalways are last for both ascending and descending. Forfirst, the rows withnullare always first. This is implemented by addingNULLS LASTorNULLS FIRSTto each sort field.Example: