MySQL Bugs: #32940: Forward Engineering skips views and routines

Bug #32940	Forward Engineering skips views and routines
Submitted:	3 Dec 2007 18:47	Modified:	17 Jan 2008 15:09
Reporter:	Heinz Schweitzer (Gold Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.0.10	OS:	Windows (xp sp2)
Assigned to:	Johannes Taxacher	CPU Architecture:	Any
Tags:	qc

Description:
Forward Engineering skips views and routines

Operating System:        Windows XP
Hardware:                Intel(R) Pentium(R) 4 CPU 2.00GHz, 1.0 GB RAM
MySQL Worknbench OSS 5.0.10 (Software Rendering)

How to repeat:

Start MySQL Workbench 5.0.10
(nothing is loaded)

Add a Table using the 'Add Table' icon
Add a view using the 'Add View' icon
Add a routine using the 'Add Routine' icon

From the main window menu say
File--> Export --> Forward Engineering SQL create script

In the window poping up just enter a file to save to.
In the next window just say finish.

---> Only tables will be exported.

In screen shot s1 you see that the Forwarding Window lists Tables, Views and Routines.

The Output Window tab, on bottom left just mentiones 'Tables and Views'

The final SQL create script file, at bottom right, only has 'Cretae Tables'.

s1

Attachment: s1.png (image/png, text), 195.59 KiB.

Thank you for the report.

Verified as described.

To repeat don't enter something into VIEW or ROUTINE definition.

Is it possible to treat this as "Not a Bug" in such a case, but as MySQL Workbench creates invalid empty table definition like "CREATE TABLE IF NOT EXISTS `mydb`.`table1` () ;" something should be fixed.

I agree with vladimir that this is expected behaviour as long as the view- and routine-editor are about to take a valid SQL-statement to define the desired object. But thats not very obvious to the user ...

So please output comments for processed emtpy objects that one can see in the SQL-Script that all objects were processed.

SQL generation for empty views and routines was improved, now a comment with the object name is written to the output.