Details for the issue

"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.

I'm opening this issue because:

• DB4S is crashing
• DB4S has a bug
• DB4S needs a feature
• DB4S has another problem

I'm using DB4S on:

• Windows: ( version:10 Pro_ )
• Linux: ( distro: ___ )
• Mac OS: ( version: ___ )
• Other: ___

I'm using DB4S version:

• 3.10.1
• 3.10.0
• 3.9.1
• Other: ___

I have also:

• Tried out the latest nightly version: https://github.com/sqlitebrowser/sqlitebrowser#nightly-builds
• Searched for an existing similar issue: https://github.com/sqlitebrowser/sqlitebrowser/issues?utf8=%E2%9C%93&q=is%3Aissue%20