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
When a database has too many tables, it's easy to solve: increase the maximum to display. However, most site admins will have trouble finding the setting.
@jcameron: @iliajie explained to me that this is not simple to address with the current design so just adding here as a longer term issue.
Thanks!
The text was updated successfully, but these errors were encountered:
I believe we need to switch to using the new table pagination API that I added some time ago. We are currently using it in "Users and Groups" module only.
The reason for this limit is that for each table or DB we display, Webmin has to fetch the number of tables and rows respectively to generate that table. And this can get pretty slow, even if we use a paginated display.
And this can get pretty slow, even if we use a paginated display.
Counting tables/indexes is almost instantaneous, but counting rows and fields can be slow. For paginated tables, could we count only the rows and fields on the current page while using the total number of tables/indexes to build the pagination itself?
When a database has too many tables, it's easy to solve: increase the maximum to display. However, most site admins will have trouble finding the setting.
![Image](https://private-user-images.githubusercontent.com/1004261/408720253-d42a0aeb-0f9c-424e-87b0-c6647544a019.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1OTkzOTQsIm5iZiI6MTczOTU5OTA5NCwicGF0aCI6Ii8xMDA0MjYxLzQwODcyMDI1My1kNDJhMGFlYi0wZjljLTQyNGUtODdiMC1jNjY0NzU0NGEwMTkucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxNSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTVUMDU1ODE0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NDRmYWJjMjgyNDRlYTQwMWRhMjU1MTMzNzk3ZjNiYjJjZjU4NDM2YzBhMTIwZTA5NzAxNjExODQyYWFhZjUxMSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.bsdKPfyebhu_QbrEQsFhhHWNZepuyhMGKvGjfTGY020)
@jcameron: @iliajie explained to me that this is not simple to address with the current design so just adding here as a longer term issue.
Thanks!
The text was updated successfully, but these errors were encountered: