Export all data with client side for more than 2000+ data, it takes longer time and pagination is destroyed
See original GitHub issueIssue Scenario
table options used are as below
searchTimeOut: 300,
pagination: true,
refresh: true,
showRefresh: true,
showExport: true,
exportDataType: "all",
//refreshOptions: {
// exportDataType:'all',
//},
exportTypes: ['csv'],
exportOptions: {
ignoreColumn: [6], // Ignore index arrays for some columns
fileName: "sampleCsvFile",
},
url: "some_url_route",
method: "get",
dataType: "json",
dataField: "search_result",
Actual Scenario for the issue Data in the table are around 5000 plus. When clicking the CSV Export button, it takes really long time to compile csv file and after export is done, pagination row is destroyed along with table info row on the bottom of the table. In fact there is no pagination implemented on the page, the whole rows of data are shown there in the single page which we can see just by scrolling down We have to refresh whole page to toggle back the pagination in such case.
Querry:
- Can you please help me understand this issue. I would like to get pagination toggle back right away the export all is done without any such issues
- I would also like to know how can I swipe the positions for refresh button and Export button?
Thanks a lot in advance.
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (5 by maintainers)
Top Results From Across the Web
soql - What are the limitations of number of Rows that can be ...
Instead of client side paginating , prefer server side pagination so you can limit the rows of data returning.
Read more >Pagination guidelines - GitLab Docs
Offset-based pagination is the easiest way to paginate over records, however, it does not scale well for large database tables.
Read more >The End of Pagination - Coding Horror
The scroll bar, the user's moral compass of "how much more is there?" doesn't work in endless pagination because it is effectively infinite. ......
Read more >Export data to CSV in server pagination / sorting / filtering mode
i think only the data visible in the viewport can be exported to csv/excel because the entire data is not available at one...
Read more >How Big is TOO BIG for JSON? - Josh Zeigler
Most developers know by now that JavaScript Object Notation (JSON) is the best way to work with data sets in JavaScript. Yesterday, I...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sure i noticed that the browser hangs up for some seconds, thats because of the 8000 (!!) Rows. For larger Datasets we suggest to export it by the server not by the client(browser).
@wenzhixin 谢谢!我使用下面这段来导出全部数据