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
Original TRAC ticket 4011 reported by valya
Hi,
I found that by default DBS3 returns unsorted lists, e.g. runs API. Even though it is not a problem per-se but it would be nice if DBS3 put in SQL statements the GROUP BY clause for entity in question and return to the client sorted list. For some API it is clear, e.g. datasets API should return ordered dataset names, runs API should return ordered run numbers, while for detailed APIs, e.g. filesummaries it is not really required.
The information I need to handle in DAS is quite large and doing extra database job is a waste of time/resources.
The text was updated successfully, but these errors were encountered:
Author: valya
May be it can be done by using extra API parameters, e.g. sort. The same principle can be applied to get pagination, e.g. idx/limit parameters. These are generic parameters and can be added to all APIs by default. But I let you decide if it is permissible.
Original TRAC ticket 4011 reported by valya
Hi,
I found that by default DBS3 returns unsorted lists, e.g. runs API. Even though it is not a problem per-se but it would be nice if DBS3 put in SQL statements the GROUP BY clause for entity in question and return to the client sorted list. For some API it is clear, e.g. datasets API should return ordered dataset names, runs API should return ordered run numbers, while for detailed APIs, e.g. filesummaries it is not really required.
The information I need to handle in DAS is quite large and doing extra database job is a waste of time/resources.
The text was updated successfully, but these errors were encountered: