You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
kevinstadler
changed the title
Implement ordering (via QueryParameters argument)
Implement ordering of results (default order and through QueryParameters argument)
Dec 11, 2024
Note: If ordering should be possible 1. via query parameters and 2. model_config, then query parameter ordering should take precedence over model_config orderings.
We discussed possible ordering by all scalar fields, i.e. also scalar fields of potentially nested models. This introduces the significant problem of how to handle alias name clashes though. So I am for restricting order-able fields to the top model scalar fields.
It is still possible to order by arbitrary SPARQL bindings through the model then, i.e. by using excluded fields in the top model. See e.g. the ungrouped wikidata example.
Ordering of results should be possible based on a single scalar field of the root model.
The text was updated successfully, but these errors were encountered: