MySQL Bugs: #65322: Bug when copying table sql to clipboard

Bug #65322	Bug when copying table sql to clipboard
Submitted:	15 May 2012 20:46	Modified:	30 May 2012 20:38
Reporter:	Scott Nelson	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S2 (Serious)
Version:	5.2.40	OS:	Windows (Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
Sometimes this feature works, but most of the time it doesn't.  When you have a table created in a schema and want to copy the SQL to clipboard, meaning the create table command used in query browser, it generates a bug.  This will continue to error each time you try.  Also after trying to exit workbench, the process stays running and I have to end it through task manager.

How to repeat:
Open a model that has tables, right click a table, click "Copy SQL to Clipboard".  Sometimes it works, sometimes it errors.  Once it errors, it will not work anymore.

Hello Scott,

Can you please add the details of the table you got the error with?

Thanks in advance!

Hi, here is the details of the table:

CREATE  TABLE IF NOT EXISTS `s_server_schema`.`tbl_rss_feeds` (
  `id` INT UNSIGNED NOT NULL ,
  `client_id` INT UNSIGNED NOT NULL DEFAULT 0 ,
  `server_id` INT UNSIGNED NOT NULL AUTO_INCREMENT ,
  `timestamp` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ,
  `removed` TINYINT UNSIGNED NOT NULL DEFAULT 0 ,
  `rf_type` TINYINT UNSIGNED NOT NULL DEFAULT 1 ,
  `rf_active` TINYINT UNSIGNED NOT NULL DEFAULT 0 ,
  `rf_name` VARCHAR(255) NOT NULL DEFAULT 'New feed' ,
  `rf_feed_items` LONGTEXT NOT NULL ,
  `rf_created` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00' ,
  `rf_modified` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00' ,
  PRIMARY KEY (`id`) ,
  INDEX `field_indexes` (`rf_type` ASC, `rf_active` ASC, `client_id` ASC, `server_id` ASC, `timestamp` ASC, `removed` ASC) )
ENGINE = MyISAM;

Getting the above I re-opened the WorkBench and right-clicked the table and clicked "SQL to Clipboard", which did copy it to the clipboard but it also generated the error in this bug.  So it seems the copying of data to the clipboard is working, but something else afterwards?

duplicate of bug #64881

With so many duplicate bug reports, will this be addressed in the next release?  I find it helpful to copy the table details to clipboard for testing on my dev machine from the schema.