Bug #42391 | Forward Engineer to SQL Script output options enhancement | ||
---|---|---|---|
Submitted: | 27 Jan 2009 19:27 | Modified: | 19 Oct 2009 11:44 |
Reporter: | Bastian Grupe | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Workbench | Severity: | S4 (Feature request) |
Version: | 5.0.29 OSS | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | CHECKED |
[27 Jan 2009 19:27]
Bastian Grupe
[30 Jan 2009 11:39]
Susanne Ebrecht
Many thanks for writing a feature request. We will discuss this.
[30 Mar 2009 19:33]
Jake Chung
I recently bought a commercial license for Workbench, and have had similar sentiments as the original poster. Before using Workbench, I used CASE studio, which did save all the export settings for each project. This feature would be a great time saver.
[24 Jun 2010 8:38]
Iain Brazendale
I'd also like to request this feature, it's been sorely missed since I started using Workbench. Is there any way to push the priority up for this feature? I noticed that it was first requested in March 2008 (bug #34977) and it seems a long time to wait for such a useful feature to be added.