Bug #48338 Forward engineering is doing nothing
Submitted: 27 Oct 2009 7:07 Modified: 27 Oct 2009 7:31
Reporter: Susanne Ebrecht Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version: OS:Any
Assigned to: CPU Architecture:Any
Tags: TTREV

[27 Oct 2009 7:07] Susanne Ebrecht
Description:
Take two MySQL instances.

In my test scenario I run one instance on port 6951 and another on port 5151.

Connect to one instance via CLI (I used port 6951):

DROP DATABASE IF EXISTS foo;
CREATE DATABASE foo CHARACTER SET utf8;

CREATE TABLE t(i integer, j integer, n integer, primary key(i));
CREATE TABLE t2(i integer, j integer, n integer, primary key(i));
CREATE TABLE t3(i integer, j integer, n integer, primary key(i));
CREATE VIEW v AS
SELECT t.j, t2.n FROM t, t2 WHERE t.i=t2.i;
CREATE VIEW a AS
SELECT t3.i, v.n FROM t3, v WHERE t3.j=v.j;

Now open Workbench 5.2.

Reverse engineer database foo (in my example by connecting to port 6951).

Change nothing.

Forward Engineer and change connection here to the other instance (in my example to port 5151).

Usually now the whole database should be created and forwarded to the other instance.

But nothing happens.

The script is empty and also when you connect via CLI to the other instance (in y example to port 5151).

SHOW databases;
You will not find a database named foo :(

How to repeat:
See above

Suggested fix:
Ask first for connection and then compare with existing/not existing database
[27 Oct 2009 7:31] Susanne Ebrecht
All works fine here by using Synchronize Model instead of Forward Engineering so I will close this bug report here.