Page 1 of 1
adding index on table with autoincrement
Posted: Sat 05 Mar 2011 22:30
by sipe16
When adding an index on a table with primary key auto_increment, it looks like it's using the following command to force index update:
CHANGE COLUMN id id INT(11) NOT NULL
therefore dropping the auto_increment.
// cyle
Posted: Mon 07 Mar 2011 07:39
by Viktor
What exact version of dbForge Studio for MySQL are you using?
Posted: Thu 10 Mar 2011 12:07
by sipe16
Using 4.50.331
Posted: Thu 10 Mar 2011 14:22
by Viktor
Yes, this is a bug.
Fix of the error will be included in the next build of dbForge Studio for MySQL.
Posted: Fri 11 Mar 2011 09:18
by sipe16
Super! Thanks
Posted: Thu 17 Mar 2011 07:35
by Viktor
The new build of dbForge Studio for MySQL, v4.50.342 is available for download. Check that problem was fixed, please.
adding an index on a table with primary key auto_increment
Posted: Tue 29 Mar 2011 15:31
by shartley
It looks like the issue was fixed when adding an index, but still exists when editing an index. I have the most recent version of the software (4.5.342 Professional Edition) and this happened to me yesterday on my production system. It caused some real issues this morning. I just tested this issue on my development system and after editing an index the auto_increment attribute was gone.
I do really like this software. It has saved me countless hours.
Posted: Wed 30 Mar 2011 07:07
by Alexz
Yes, you are right. We've reproduced this problem. It will be fixed in the next build of the product. We plan to release it today.
We'll inform you when the new build is available for download.
Posted: Fri 01 Apr 2011 08:02
by Alexz
The problem was fixed. The new build (v4.50.348) is available for download.