1) create a table with a little data in it
2) open it with the "data" tab
3) click the "filter" button, and enter an invalid filter (but don't apply it)
4) click one of the columns in the data table, causing an ORDER BY query
HeidiSQL will now attempt to order the data, using the bad filter. A dialog box will be shown about the invalid sql statement (which is ok), after which HeidiSQL crashes (not so ok).
I ran into it by mistake. As it's unlikely to happen to very many people, I'd say that it's minor - but it feels like it should also be quick and easy to fix. I'm using 9.3.0.4984 under wine on Debian Linux.
3 attachment(s):