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
"View - Preferences - Database - Prefetch block size" creates unsafe grid selection.
And the ? tool does not work within the preferences dialog to describe the ramifications of this setting?
At a minimum, the Results window should state:
XXX rows of YYY available returned in Nms from: select * from myDB;
Better is to return all rows when user clicks Select All [Ctrl+A] or clicks the upper left of the grid box.
This is tricky behavior.
I understand the desire to limit rows for performance, but "Select All" must = "All".
Not "Select All loaded rows".
Useful extra information
Set the Prefetch to a smallish number like 500.
Execute a SQL statement that returns more than 500.
The Results window tells the user XXX rows returned in Xms from: select * from myDB;
Select all resulting rows & cols - Copy to clipboard.
Result = Only the prefetch amount of rows were selected and copied.
Scrolling beyond the prefetch amount appends additional prefetch rows.
But this is an intensive and unexpected operation to get "all" the returned rows.
Sorry to bump topic, but I wanted to request this as BUG and not Enhancement?
This can really cause errors down the line if users select all and get only 500 records.
There should be a popup message saying "NOT all" records selected.
@sky5walk I've polished this change, which I have left for a time in a repository copy, and have pushed it to the master branch. It will in tomorrow's nightly build.
Whenever "Select All" is requested through keyboard shortcut or the upper-left corner, if there is data still to be loaded, it asks the user whether to continue or cancel the selection. If accepted, all the data is loaded before performing the actual selection. Then copy and paste work as expected. Plea.se, confirm it's working OK for you.
Thanks for the additional prompts and the progress bars!
I tested with ~2.5M rows and now it is very clear what DB4S is delivering.
Please close this ticket.
Activity
justinclift commentedon May 2, 2018
Yeah, thinking about it a bit more, that does make sense. 😄
sky5walk commentedon May 24, 2018
Sorry to bump topic, but I wanted to request this as BUG and not Enhancement?
This can really cause errors down the line if users select all and get only 500 records.
There should be a popup message saying "NOT all" records selected.
justinclift commentedon May 24, 2018
No worries @sky5walk. 😄
Load all data when select all is requested
mgrojo commentedon Dec 15, 2018
@sky5walk I've polished this change, which I have left for a time in a repository copy, and have pushed it to the master branch. It will in tomorrow's nightly build.
Whenever "Select All" is requested through keyboard shortcut or the upper-left corner, if there is data still to be loaded, it asks the user whether to continue or cancel the selection. If accepted, all the data is loaded before performing the actual selection. Then copy and paste work as expected. Plea.se, confirm it's working OK for you.
sky5walk commentedon Dec 15, 2018
Thanks for the additional prompts and the progress bars!
I tested with ~2.5M rows and now it is very clear what DB4S is delivering.
Please close this ticket.