Ticket #300 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

orderby on collection produces incorrect result

Reported by: Michiel.Schok Owned by: arjen
Priority: minor Milestone: MediaMosa 2.1
Component: Core Version: 2.1.3
Keywords: Cc:
MoSCoW: none Estimated time after impact analysis:
Related to project: none Tested: yes
Accepted: yes Estimated Hours:

Description

When trying to get the 'biggest' collections (the collections with the most assets in it), I used the call

[GET] collection?order_by=numofvideos&order_direction=desc&limit=100

regardless of the 'order_direction' (desc|asc), the topmost results have all '0' videos in it, and the list seems sorted 'ascending'.

Change History

Changed 3 years ago by forgacs

  • owner set to forgacs
  • status changed from new to assigned

Changed 3 years ago by forgacs

  • owner changed from forgacs to arjen

It is fixed. It is on my repository.

Changed 3 years ago by MC-arjen

  • status changed from assigned to closed
  • version set to 2.1.3
  • resolution set to fixed

committed

Changed 3 years ago by Michiel.Schok

  • tested changed from no to yes
  • accepted changed from no to yes

The order is now as expected.

Note: See TracTickets for help on using tickets.