Bug #46262 Export INSERT statements doesn't work
Submitted: 17 Jul 2009 12:34 Modified: 17 Jul 2009 14:40
Reporter: Denis SORIANO Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.1.16 OS:Windows
Assigned to: CPU Architecture:Any
Tags: export, insert

[17 Jul 2009 12:34] Denis SORIANO 
Description:
High All,
It seems that export the INSERT statements doesn't work.
They're not in the exported file, neither in the review generated script.
I note that when I right click on a table and I select "Copy Insert to Clipboard", the clipboard contain an empty request...

How to repeat:
Go to File > Export > Forward Engineer SQL CREATE Script.
In the SQL Export Options, check "General INSERT Statements for Tables", then continue the export.
[17 Jul 2009 14:40] MySQL Verification Team 
Thank you for the bug report. Related to the bug: http://bugs.mysql.com/bug.php?id=46232.
[21 Jan 2010 19:25] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/97772

3065 Konstantin Osipov	2010-01-21
      Bug#46262 review comments: remove unnecessary friends.
[22 Jan 2010 9:34] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/97814

3063 Konstantin Osipov	2010-01-22
      Bug#46272 review fixes: remove an unnecessary friend.
      ******
      Bug#46272, review comments, remove an unused friend.
      ******
      Bug#46262 review comments: remove unnecessary friends.
      Bug#46272: change wait_for_locks() to wait for one lock only.
[22 Jan 2010 21:05] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/97940

3058 Konstantin Osipov	2010-01-23
      Bug#46262, post review fixes.
      Fix a bug when we would prematurely release the global shared lock
      ticket in scenario:
      
      flush tables with read lock;
      lock table t1 write; <-- here we call unlock_locked_tables(), which
      clears the sentinel, and releases the global shared lock.
      
      Move the global read lock into a separate class.
      Remove redundant is*owner() methods from MDL_context.
[25 Jan 2010 16:48] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/98099

3058 Konstantin Osipov	2010-01-25
      Bug#46262, post review fixes.
      Fix a bug when we would prematurely release the global shared lock
      ticket in scenario:
      
      flush tables with read lock;
      lock table t1 write; <-- here we call unlock_locked_tables(), which
      clears the sentinel, and releases the global shared lock.
      
      Move the global read lock into a separate class.
      Remove redundant is*owner() methods from MDL_context.