distal-attribute
distal-attribute
distal-attribute
distal-attribute

unsuccessful update from 8.3.0.46xx to 8.3.0.47xx

baursak posted 5 months ago in General
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...
kalvaro posted 5 months ago
Do you mean that table indexes show up as phantom columns in the "Columns" pane?

That's really weird...
baursak posted 5 months ago
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...
ergeka posted 5 months ago
The same here. Downgraded to 8.3.0.4790. It looks not intentional.
arucard posted 5 months ago
Last "good" revision is #4792. Next ones have this bug.

scorpio4264 posted 5 months ago
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.
baursak posted 5 months ago

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


I confirm that revision #4792 is "good".
alesvaupotic posted 5 months ago
+1 for #4792.
scorpio4264 posted 5 months ago

baursak wrote:

arucard wrote: 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.
scorpio4264 posted 5 months ago
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.

ansgar posted 5 months ago
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.
ansgar posted 5 months ago
r4795 should fix that column confusion.
ergeka posted 5 months ago
Thanks. smile
baursak posted 5 months ago

ansgar wrote: r4795 should fix that column confusion.


Thank you for encouragement.
scorpio4264 posted 5 months ago
Yep, r4795 did it! Thanx a lot for quick turnaround

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