-
Sub-task
-
Resolution: Duplicate
-
Neutral
-
None
-
None
-
None
Using an enum for "fields" that we can order by seems like the sanest option that should be portable across providers. For other cases, one can always resort to provider-specific queries.
Also add an asc/desc option (or find good defaults)
TBD: support for multiple orderBy
- is duplicated by
-
MGNLDAM-546 AssetQuery: add sorting capabilities
- Closed