pgadmin-org
Select all rows in results grid should allow copy
Describe the bug
Assuming I have a result set with more than the configured "Data result rows per page", I click the upper left corner of the grid to select all rows. This selects just the rows in the batch, but offers a button labeled "Select All N Rows". If I click that button, a message is shown stating "All N rows are selected". However, the Copy button is disabled, so I can't actually copy the rows.
To Reproduce
Steps to reproduce the behavior:
- Rows per page is set to 1000
- I run a query that has 24945 results
- Click on the empty space above the row numbers to select all rows
- Click on the button labeled "Select All 24945 Rows"
Expected behavior Copy button should be enabled, allowing me to copy these rows.
Screenshots
Desktop (please complete the following information):
- OS: Windows-11-10.0.22631-SP0
- Version: 8.13
- Mode: Desktop
Additional context
My employer manages our PGAdmin install. Not sure what version I had previously but it didn't have this paging system. In that version, I could just click the space above the row numbers twice and the entire result set would be loaded.
I can work around this new issue by editing the range but I find this less convenient than the way it worked before.
Hi @DanielPiersonLN, Previously, when select all was clicked the UI fetched all the rows from server. This is not the case now. For performance reasons, only page data will be loaded in UI. What can be done is when copy is clicked (with select all) - change the page range to fetch all the rows and then copy the data. As a workaround, you can either increase the page size from preferences or change the range from data output.
If it's performance related why can you still load all records to UI by manually entering the record count? I would strongly suggest clicking the "Select All Rows" would load all records to UI. From a data analytics perspective the current functionality leaves room for mistakes in copying data, which can potentially result in critical errors.
If it's performance related why can you still load all records to UI by manually entering the record count? I would strongly suggest clicking the "Select All Rows" would load all records to UI. From a data analytics perspective the current functionality leaves room for mistakes in copying data, which can potentially result in critical errors.
@mthanasides We cannot force the users to see only and only 1000 rows - thats where you can manually enter. Performance is based on how many rows are loaded in the UI. Like I mentioned above As a workaround, you can either increase the page size from preferences or change the range from data output.