Back contributions from integrations (MGNLDAM-549)

[MGNLDAM-405] AssetQuery: add orderBy Created: 25/Feb/14  Updated: 01/Jul/15  Resolved: 12/May/15

Status: Closed
Project: Magnolia DAM Module
Component/s: DAM API, DAM JCR Provider
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Neutral
Reporter: Magnolia International Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by MGNLDAM-546 AssetQuery: add sorting capabilities Closed
Template:
Date of First Response:

 Description   

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



 Comments   
Comment by Robert Šiška [ 12/Mar/15 ]

Fixed in (accidentaly created) duplicate MGNLDAM-546

Comment by Magnolia International [ 12/May/15 ]

(reopening to fix resolution)

Generated at Mon Feb 12 04:59:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.