Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Inconsistent/counterintuitive count of rows and columns in results between tab title and selected cell in toolbar #712
Steps to reproduce this issue
The row/column count is inconsistent in order, because one show column then row, and the other the opposite. Plus, it is not intuitive to deduce which number is row or column
Both cases should show at least be in the same order. Or better, to indicate what each number means.
Change the order of either one to match the other. This has the disadvantage of still not being intuitive to recognize each.
Additionally, just add a label indicating which case each number means, e.g.
and in status bar:
This way with only a glimpse it would be clear, both the global count and the current selection coordinates.
What about using some Unicode arrow characters for that purpose:
Whether that does not show a broken character will depend on the selected font, and probably Wine has problems with it, not sure. But at least Tahoma and Segoe on Windows 10 seem to support these arrows.
Check out the next build to see it yourself.
Could be a Wine issue then, although the font is the same.
Could you please go to Tools > Preferences > General, and select a different GUI font, to see if that makes a difference?
I can also try and use hex codes instead of real Unicode characters in the code, to prevent read errors.
i too experience this confusion (most often with small result sets where the numbers are close), but i'm not a huge fan of the proposed solution. the arrows are tiny and the vertical one resembles a "1" which is even worse. in addition, i very rarely care about the column count in a grid or query result and always care about the row count. IMO, rows should always come first and if you feel that columns are important enough to always show, then maybe
Update, this time I am trying from a windows machine, and here it does show them correctly:
So I guess it is indeed a Wine / fonts related problem.
However, as leeoniya mentions, it may be better to just use standard characters instead of unicode. This way you'd have the most compatibility.
As I initially suggested, a better choice would be to just use 'r' and 'c' for rows and columns:
IMO it is fairly understandable. Plus you could add a tooltip to clarify, e.g. show
Somehow unrelated. When I tried to install with the HeidiSQL_10.2.0.5693_Setup.exe file (at Windows), my Avast Antivirus detected it as a possible threat. I managed to install it by adding the installer to a white list, but then, running the program (not the installer), it again reported it as a possible threat. I overcame that by temporarily disabling the Avast shields.
This didn't happen before, but the Avast program/definitions have recently updated so I am fairly sure it is a false positive.
either way, i think showing te rows before columns is uncontroversial.
Sounds good to me. In the tab it shows as the fixed count of resulted rows and columns, and in the status bar it means the CURRENT selected cell (or the total as well if no cell is selected).
Funny, until now, I haven't noticed that if instead of the results you click/move the prompt in the query editor, the status bar also shows the current cursor position (coordinates).
And about Avast antivirus, I just got a notification that the installer has been scanned by them and found to be harmless. I guess their database didn't have such installer 'validated' yet