Bug in GUI mode Table Column editing
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 !!
Author/Founder: Traffic Squeezer.
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.
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.
Modify Mainform.SelectedTable so that it always returns a new TDBObject, instead of passing an item of the connection's internal cache. Makes sure that the object editors (table editor e.g.) still has a valid object reference. See also http://www.heidisql.com/forum.php?t=5511#p5514
Please login to leave a reply, or register at first.