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
{{ message }}
This repository has been archived by the owner on Dec 3, 2019. It is now read-only.
In the component page, all the entries load at one shot. Considering that Datatables are being used (along with features like sort, search, export), it is important that all of the contents of the database is transferred to the client side. But the number of such entries is large, hence it takes a lot of time.
@zvr@gopuvenkat Could you please share your inputs on the same.
The text was updated successfully, but these errors were encountered:
As listed in the Examples page, Datatables provides support to both Deferred loading of data and Server side processing. We will have to look into the possibility of providing features like export in such a setup.
Yes, all data should be paged on the server.
This is not only about components (where this is easily demonstrated), but for every tabular data.
And ideally it would be a user preference how large a "page" would be.
This, together with a couple of other issues (on importing and exporting data) are on the roadmap for this year's GSoC.
The current implementation is definitely not suitable for real life cases.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the component page, all the entries load at one shot. Considering that Datatables are being used (along with features like sort, search, export), it is important that all of the contents of the database is transferred to the client side. But the number of such entries is large, hence it takes a lot of time.
@zvr @gopuvenkat Could you please share your inputs on the same.
The text was updated successfully, but these errors were encountered: