feat: EXPOSED-560 Support DISTINCT ON from Postgres #2275
+120
−1
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.
Description
Added support for
DISTINCT ON
clauses in theQuery
class, enabling retrieval of distinct rows based on specified columns for SQL SELECT statements.Detailed description:
withDistinctOn(Column<*>, vararg Column<*>)
andwithDistinctOn(Pair<Column<*>, SortOrder>, vararg Pair<Column<*>, SortOrder>)
in theQuery
class to allow the use ofDISTINCT ON
clauses. These methods enable distinct rows selection based on the specified columns and optionally ordered by specified sort orders.Query
class to set thedistinctOn
property.prepareSQL
method to include theDISTINCT ON
clause whendistinctOn
is set.Type of Change
Affected databases:
Related Issues
EXPOSED-560 Support DISTINCT ON from Postgres
#500