Bug in GUI mode Table Column editing

Seems there is a bug in GUI mode table column editing. It is intermittent, so most times it works fine, but eventually once a white it comes up. Need to close HeidiSQL and do again, it works, again for 2nd column editing it comes up, again close and do all over again it works.

Here is the bug description:
A existing table when you modify a column say (colA varchar(10) to colA varchar(50), so on... it executes backend SQL alter table... but 2nd time instead of doing this it does alter table rename <some table> <actual table> colA... .
So somehow this rename comes in the wrong context this is the bug.

HeidiSQL is a great tool, we are trying new in our TrafficSqueezer.org automations. GREAT WORK guys !

Let us monopolize Open-Source !!

Cheers,
Kiran
Author/Founder: Traffic Squeezer.

Could you please update to the latest build? If I understand right that was fixed recently.

Dear Anse,

Thank you for a very swift reply, on Sunday !!

Hey I checked it, and moreover I suspect it is a bit worse I think with the new version specifically. First it happened with 2-3 columns, then with 2 columns... again after many restarts now it is 1:1 column editing I need to restart HeidiSQL.


Cheers,
Kiran

Query it generates on changing 1st column after fresh start of HeidiSQL: (so this is working Query, 2nd is non working Query)
ALTER TABLE `paypal_statement_log` CHANGE COLUMN `postage_packing` `postage_packing` DECIMAL(10,3) NULL DEFAULT NULL AFTER `item_id`;


So here is the query it generates one 2nd attempt of changing 2nd column:

ALTER TABLE `user` RENAME TO `paypal_statement_log`, CHANGE COLUMN `insurance_amount` `insurance_amount` DECIMAL(10,3) NULL DEFAULT NULL AFTER `postage_packing`;

So it dont need to insert this statement "`user` RENAME TO `paypal_statement_log`" instead it should just continue as "ALTER TABLE `paypal_statement_log`" as in the first query.

So this happens if I try to change column parameters/properties.

Can confirm that. Happened when editing a table - should also happen on procedures, triggers, views and events. However, that should be fixed in r3259.