possible bug? hidden column header displayed & disconnect detection crashes

khchan's profile image khchan posted 7 months ago in General Permalink

Hi. Quite often, i encounter below with HeidiSQL 12.4. These would be considered bugs?

  • When I have a table that has a hidden column & when i try to view data of that table, sometimes the header of the hidden column displayed (column values of that hidden column are not). This causes all headers to be shifted 1 to the right.
  • Very often when my wifi or VPN disconnects & then when i switch to heidisql, heidisql will report a problem, & either needs to abort, retry or restart. Retry for sure fails. Abort aborts as per its function, & restart restarts HeidiSQL as per its function.
ansgar's profile image ansgar posted 7 months ago Permalink

Please post a screenshot. I don't get what you mean in your first of the two issues.

khchan's profile image khchan posted 6 months ago Permalink

Hi, attached a sample. Does not always happen but happened in this case. In screenshot: First column header says RUId, but first column data is actually data of 2nd column header. 2nd column header says DB, but 2nd column data is actually data of 3rd column header... ... and so on.

1 attachment(s):
  • mismatching_columns
khchan's profile image khchan posted 6 months ago Permalink

The RUId column is a hidden column.

ansgar's profile image ansgar posted 6 months ago Permalink

Ok, the let's please update your HeidiSQL to the latest build please. Just to verify I did not already solve this issue.

khchan's profile image khchan posted 6 months ago Permalink

Hi. Just tested with ver 12.5 portable & with nightly build 12.5.0.6686. Still same.

ansgar's profile image ansgar posted 6 months ago Permalink

Ah I see now. This is due to lack of support for invisible columns in HeidiSQL. This is issue #872.

ansgar's profile image ansgar posted 6 months ago Permalink

Next HeidiSQL build will fix this, so if a table has such an invisible column, it will explicitly be mentioned in the SELECT clause, fixing the column shifting and a crash in other cases.

What is left to do is add support for creating/altering a column with the INVISIBLE flag.

khchan's profile image khchan posted 6 months ago Permalink

I had a look at issue #872. The person who reported it gave it a quite a bit of thought from a solution point of angle. Just perhaps what he's proposed could be implemented part by part over time. As for just the display portion, yep consistently ensuring that the invisible column is explicitly mentioned should do the trick. What's odd is, data of the invisible column doesn't always not appear.

khchan's profile image khchan posted 6 months ago Permalink

In this screenshot, seems things are handled generally okay. (all my tables have an auto increment invisible 1st column)

1 attachment(s):
  • Untitled
khchan's profile image khchan posted 6 months ago Permalink

In this screenshot, somehow it's just a select * & contents of invisible column aren't selected (but its header is shown)

1 attachment(s):
  • Untitled
khchan's profile image khchan posted 6 months ago Permalink

In the 2nd last screenshot, somehow the select statement already explicitly selects each column, including the invisible column (select command visible at the bottom window). In the last screenshot, it's just select *.

ansgar's profile image ansgar posted 6 months ago Permalink

You need to update HeidiSQL to the latest build in order to see it fixed.

khchan's profile image khchan posted 6 months ago Permalink

No prob. Hope it's a small effort. Thanks.

ansgar's profile image ansgar posted 6 months ago Permalink

Not sure if you got what I meant. Which build do you use? You can see it in HeidiSQL's title bar:

Description

khchan's profile image khchan posted 6 months ago Permalink

Understood your meaning. :) I'm using build 12.5.0.6677 stable portable version now. Will try the nightly builds every now & then (to check occasionally whether that latest build has the fix). And will later look for it in stable releases.

ansgar's profile image ansgar posted 6 months ago Permalink

In the build you are now using, the invisible columns should not cause the field shifting like you mentioned above. I already fixed that recently.

khchan's profile image khchan posted 6 months ago Permalink

Well, in post 6 of this topic, i already tested used the latest stable release & latest nightly build & reported in that post: "Hi. Just tested with ver 12.5 portable & with nightly build 12.5.0.6686. Still same.".

Also posting a screenshot in this post, where you can see the build number & instance of the issue all in 1 screenshot.

1 attachment(s):
  • Untitled
ansgar's profile image ansgar posted 6 months ago Permalink

Build 6677 (in your screenshot) is outdated, and 6686 (from your comment) is also outdated. If you want to see the issue fixed, you need to update to build 6687.

khchan's profile image khchan posted 6 months ago Permalink

Oh you mean you've already released a build where this is fixed. I misunderstood! Sorry. Yes just tried build 6687, the latest one, & the shifted columns issue doesn't happen anymore. Thanks again.

Please login to leave a reply, or register at first.