TL;DR: The only valid approach to this is to Client-side sorting in Javascript, with the disadvantage that you do not have complete results, only that what you already see. If this is good enough, should not be much of a problem.

Long story

How its describes is also how sorting in Files work. With the difference that all files are retrieved in background. Which is not possible for users (too many, far too slow).

In general, you can pick between two approaches:

Client side sorting

Advantage: fast, no server interaction

Disadvantage: may be incomplete, sorts only the rows that are present

Server side sorting

Background: for the provided cols, looking at preferences table is sufficient (needs to ask user backends for meta data still).

Advantage: If trying hard enough, you get a complete picture…

Disadvantage: requires server interaction → slow. Won't retrieve users without rows set, (unless you ask user backends first for all! users – no-go on big instances). Even slower (must match results from preferences table and user backends), and most likely breaks paging, is the combination with a search filter (you will have gaps and never know whether there are more users to retrieve).

Sorting of users #3230

Description

KB7777openedon Jan 24, 2017

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

KB7777
openedon Jan 24, 2017