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
Context: I have some tables with a lot of data. Actually I saw that in a table with 6100 rows, but I have some with much more. Using eager loading (laravel project) the queries return in ~1s. But the view is taking 1 minute or more to load. Inspecting, using debugbar, I saw that the view is rendering all the table components in the view (icons, buttons, etc), not only the 10 that I put to show in the paginated view. So, probably this is the origin of the delay. This is the expected behavior of the component? And if no, how can I fix this?
The text was updated successfully, but these errors were encountered:
The table component does client-side pagination. So it takes all the data you pass to it and then paginates it to prevent the user from going back to the server for more data. This may not work optimally for large datasets. The workaround for this will be to use the pagination that comes inbuilt with Laravel and then only use all other features of the table component other than pagination. Don't know if this helps.
Context: I have some tables with a lot of data. Actually I saw that in a table with 6100 rows, but I have some with much more. Using eager loading (laravel project) the queries return in ~1s. But the view is taking 1 minute or more to load. Inspecting, using debugbar, I saw that the view is rendering all the table components in the view (icons, buttons, etc), not only the 10 that I put to show in the paginated view. So, probably this is the origin of the delay. This is the expected behavior of the component? And if no, how can I fix this?
The text was updated successfully, but these errors were encountered: