unsuccessful update from 8.3.0.46xx to 8.3.0.47xx

Hi. - Today I have reinstalled my Win7x64 and installed former HeidiSQL_8.3.0.4694. - Then I created a DB and a couple of tables. - HSQL suggested to update, which I have done. - As a result I have got now HeidiSQL_8.3.0.4794 and funny new table editor interface ( https://yadi.sk/d/kdcSrKblVzLXz ). - Is this a bug or feature? - I have searched through HSQL forum and found no one complained about this...

Do you mean that table indexes show up as phantom columns in the "Columns" pane?

That's really weird...

Yes, 'table indexes show up as phantom columns in the "Columns" pane'. - It's strange, that I am the first, who complained about this in this forum...

The same here. Downgraded to 8.3.0.4790. It looks not intentional.

Last "good" revision is #4792. Next ones have this bug.

I also confirm this bug. In my case the table structure shows several additional fields which are copies of real fields in this table. For example, I can have two ID fields - the first is a real one, and it is Int(6) Auto-increment, while the fake one is Varchar.

The good news is that a query "SHOW CREATE TABLE xxx" is still producing a proper result.

Last "good" revision is #4792. Next ones have this bug.

I confirm that revision #4792 is "good".

+1 for #4792.

Last "good" revision is #4792. Next ones have this bug.

I confirm that revision #4792 is "good".

Sorry, guys. I had to go back one version by one down to #4784 till my problem with wrong table structure was gone. So I insist that only revision #4784 is good, the rest expose this bad column name report.

Well, I need to be more clear, not to confuse anybody: there are two problems with table structure report, one is wrong report of the column name and its other properties, but at least the number of fields matches the reality - it started from #4785, and then the other problem shows up when the number of fields is increased by copies of some existing fields. This one may show up after #4792.

Well, that's obviously broken since my r4793 update, which should have only fixed support for column names with backticks in them. The logic seems to include keys and foreign keys as columns.

r4795 should fix that column confusion.

Thanks.

r4795 should fix that column confusion.

Thank you for encouragement.

Yep, r4795 did it! Thanx a lot for quick turnaround