MySQL Bugs: #35354: error in export SQL syntax

Bug #35354	error in export SQL syntax
Submitted:	17 Mar 2008 22:55	Modified:	18 Apr 2008 4:19
Reporter:	Philipp Guillaume	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.0.15 OSS RC	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	export, script

Description:
Impossible to export a table from MySQL Workbench.
Using right-click->Copy SQL or the export menu.
Lot's of syntax error. Here is an example : 

CREATE  TABLE IF NOT EXISTS `easy_share`.`users` (
  `user_id` SMALLINT UNSIGNED NOT NULL AUTO_INCREMENT COMMENT 'Identification unique de l utilisateur' ,
  `user_login` VARCHAR(125) NOT NULL ,
  `user_email` VARCHAR(255) NOT NULL ,
  `user_firstname` VARCHAR(125) NOT NULL ,
  `user_lastname` VARCHAR(125) NOT NULL ,
  `user_password` VARCHAR(255) NOT NULL COMMENT 'Crypter en sha1' ,
  `user_ip` VARCHAR(15) NOT NULL ,
  `user_date` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT 'Date d inscription' ,
  `user_lastlogin` TIMESTAMP NOT NULL COMMENT 'Derniere connection' ,
  `user_grade` SMALLINT UNSIGNED NOT NULL DEFAULT 0 ,
  `user_storage` SMALLINT UNSIGNED NOT NULL DEFAULT 0 ,
  PRIMARY KEY (`user_id`) ,
  INDEX user_id () )
ENGINE = InnoDB
AUTO_INCREMENT = 0
DEFAULT CHARACTER SET = utf8
CHECKSUM = 1
COLLATE = utf8_unicode_ci
PACK_KEYS = DEFAULT

______________
Mysql error :

Documentation
#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') )
ENGINE = InnoDB
AUTO_INCREMENT = 0
DEFAULT CHARACTER SET = utf8
CHECKSUM' at line 14 

This is an error with one table. But it's the same think with all of my project.
The first .wpf was created with 5.0.14a.

Thanks a lot for all your work.

How to repeat:
Just try to export a table created with MySql Workbench

All my table.

Attachment: Ci.mwb (application/octet-stream, text), 13.71 KiB.

Thank you for a problem report. You had created index user_id, but had not selected any column(s) to index. Hence this syntax:

INDEX user_id() )

and error message. I think this is not a bug, just user's mistake.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".