MySQL Bugs: #34827: Skipping schema name when creating SQL script

Bug #34827	Skipping schema name when creating SQL script
Submitted:	26 Feb 2008 11:49	Modified:	28 Aug 2009 7:40
Reporter:	Dejan Krsmanovic	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S4 (Feature request)
Version:		OS:	Any
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	CHECKED

Description:
I would like to be able to forward engineer SQL script without schema information. 
Currently, we have a project where several schemas contain same tables. In DBDesigner we were able to create script that could be executed in different schemas, but with MySQL Workbench this is a problem. 

How to repeat:
Click on File/Export/Forward Engineer SQL CREATE Script

Thank you for a reasonable feature request.

Is this feature request still on the radar? 
I'm in desperate need of this functionality and would be grateful if it was realized any time soon.

Thanks a lot,
Martin Simons

Hi, 

It would be very very helpful for our database management if you can add this feature soon.Atleast please let us know the time line that you are shooting for a this feature so that we can have an idea until when would have to wait.

It would be very nice of you if you can add this feature as soon as possible.

Thanks in advance,
Surya Kuchibhotla.

I'd find this feature useful too.

The name of the database in workbench dictates the schema name that is deployed to, but it's entirely possible that the schema name in the target database differs from this.

One example is where - as I do - there are two differently named schemas in the same database instance, one that is targeted by a development version of a web application and another that is the target of an automated test suite.

Another example is one where the target schema name is not fully under the control of the developer (i.e. is dictated by the ISP who hosts the production site)

Fixed in 5.1 and 5.2

option is called "omit schema qualifier in object name".
please be aware that wb doesn't change script used in procedures/views. so if you are using schema qualifiers in these location you'll have to remove them manually.
fixed in 5.1.17

A 'change' entry was added to the 5.1.17 changelog:

In MySQL Workbench it was not possible to generate an export script without schema information. MySQL Workbench has been changed to include the option Omit Schema Qualifier in Object Names. This can be found in the Forward Engineer SQL Script and Forward Engineer to Database wizards.

Note that this does not change the script used in Procedures or Views. If you are using schema qualifiers in these locations you will have to remove them manually.