Warn when sorting large table by non-indexed column

[hkaraoglu]

Steps to reproduce this issue

1. Step 1;
   Open a table that has a binary column.
2. Step 2;
   Click on binary column to sort data.
3. Step 3;
   If you have big data on this column or many rows on this table, it crashes after a while.

Current behavior

When I click on binary or blob data column accidently, it tries sort data by this column. But this column has big data and no need to sort it. Because it stores binary (file, image or another). That's not meaningful to sort.

Possible solution

Disable sort for binary and blob column.

Environment

• HeidiSQL version:
  10.1.0.5464 (64Bit)

• Operating system:
  Windows 10

[ansgarbecker]

There may be tables out in the world which store smaller things than images in blobs. So I'm heavily against disabling the possibility to "sort by accident".

What Heidi may do here is to warn the user, if the column has a large data type (blob and text) AND if the table's size is over 100M or so.

[ansgarbecker]

Or, even better: As sorting by non-indexed columns is generally slow, Heidi could warn if the column is not indexed (plus the table has >100M)

[Ivan-Perez]

Giving the ability to stop the query (and reset the sort order) if it takes too long to load the data would be a good idea aswell. Currently, the program freezes when the server takes several minutes to sort the data on huge tables.

[ansgarbecker]

Related: issue #1868, now fixed, resets a previous sort order on a table before opening the data tab.