Database retrieval in Datagrid/Listview/gallery:
When retrieving data in a datagrid/listview/gallery we have several options like pagesize and pagination etc., and it is possible to create an offset to minimize the returned data, but this should be easier.
When the page is loaded and we see 200 results with 20 results a page. Who will click 'next' through all those 10 pages? I believe that people are willing to click 'next' for 2-3 times if they know that the data might be there. If not everybody will want a search menu/item to find their required data.
So to enhance performance why do we load the entire database, that is contained in the query?
I would like to suggest a page-offset function inside those Widgets.
For example:
I have a query that returns 5000 results, i would like to give the page-size and quantity of pages to the widget. The widget will only load those results while still maintaining the pagination.
So PageSize: 20 and PageQty: 5 will only load the first 100 results of the query, but the pagination of the grid is still the same as it is now.
Firstpage says 1 to 20 of 5000 and when u go to the next it would say 21 to 40 of 5000.
Benifits:
- The quantity of results is kept minimal and therefor enhances performance.
- The PageSize/Qty will give the user control. Depending on the data, one might load more/less data at once.
- When inside the widget no helpers are needed to alter the offset/amount in a retrieve
* Is it possible to pass these to a DS_microflow?? (i do not know)
- When using a filter the returned results are most likely to be less then the pagesize/qty and will load faster.
There might be even more benefits to it, but these are the first for which this idea might help users.