It is quite hard to look for changes in certain rows when it is not feasible to filter and sort so that the interesting rows are close to the top of the table.
I have four propositions to make tracking specific changes easier when reloading with <CMD+OPT+R>:
1) maintain the scroll position - this will make it easier to track changes for currently visible rows/columns
2) maintain the selected rows (for tables with primary keys) - this will make it easier to track changes for over rows even if some are not currently visible
3) don't clear the table view on pressing <CMD+OPT+R>, instead disable/grey-out the view - this will make it easier to track the text changes in the currently visible cells
4) don't recalculate column width - it's easiest to track changes if everything stays at the same position
For an idea on how it could work, Sequel Pro does this to perfection. It makes debugging much easier, particularly if you're continuously editing JSONB values and watching for specific nested changes.
It is quite hard to look for changes in certain rows when it is not feasible to filter and sort so that the interesting rows are close to the top of the table.
I have four propositions to make tracking specific changes easier when reloading with <CMD+OPT+R>:
1) maintain the scroll position - this will make it easier to track changes for currently visible rows/columns 2) maintain the selected rows (for tables with primary keys) - this will make it easier to track changes for over rows even if some are not currently visible 3) don't clear the table view on pressing <CMD+OPT+R>, instead disable/grey-out the view - this will make it easier to track the text changes in the currently visible cells 4) don't recalculate column width - it's easiest to track changes if everything stays at the same position