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
I understand how to use insert() in order to add new rows, which works great when I simply want to load a bunch of data remotely.
But if the data is big it can become slow, so obviously I can just load part of that data. But then the datatable is only showing the partial data, and the pagination is related to the partial data.
If the library had a way to know the maximum number of items, the pagination could be based on that number, rather than the number of actual items. Of course, if someone clicked on a page (or sort, filter, etc.), it would need to make a callback to properly fetch the data.
I realize this isn't trivial, but would be a cool feature.
The text was updated successfully, but these errors were encountered:
@tacman I agree, that would be a nice addition. However, with a lot of the data not being available, the table cannot really do a lot of calculations, for example how wide a specific column should be given some settings, etc. .
Makes sense. it could default to treating the first X number of rows (from the ajax source) as if the data were in the HTML. Or allow the developers to set those attributes. Just brainstorming.
I understand how to use insert() in order to add new rows, which works great when I simply want to load a bunch of data remotely.
But if the data is big it can become slow, so obviously I can just load part of that data. But then the datatable is only showing the partial data, and the pagination is related to the partial data.
If the library had a way to know the maximum number of items, the pagination could be based on that number, rather than the number of actual items. Of course, if someone clicked on a page (or sort, filter, etc.), it would need to make a callback to properly fetch the data.
I realize this isn't trivial, but would be a cool feature.
The text was updated successfully, but these errors were encountered: