MySQL Forums
Forum List  »  MySQL Workbench

Re: schema to a db in mysql administrator
Posted by: Mike Lischke
Date: February 18, 2009 02:32AM

Hey Fabian,

it is important to consider that you will never add anything to MySQL Administrator (except maybe for new graphs, but that is another matter). MA is a tool to show and let you work with a MySQL server and its objects. That means if you want to see a new schema in MA then you have to add this to your server first (you can use MA for that, but there are many other ways to accomplish this task).

Now when you created a model in MySQL Workbench (WB) you can create a physical instance of it in form of one or more schemata. This is called "forward engineering". This can be done in two ways. Either let WB create an SQL script for your model which you can load into MySQL Query Browser (QB) or use the command line interface (CLI) to do that, and which will then execute this script and create whatever objects are contained in this script.

When you have the standard edition (SE) version of WB then you can do that even more conveniently: simply do the forward engineering to a direct database connection. So it will end up directly in your schema instead of taking the extra step of using a script.

In either case, when you are done you can open MA and you will see the new objects. If you left open MA while you did the forward engineering then you will have to manually refresh the schemata list (see context menu in the list of schemata).

Mike

Mike Lischke, MySQL Developer Tools
Oracle Corporation

MySQL Workbench on Github: https://github.com/mysql/mysql-workbench
On Twitter: https://twitter.com/MySQLWorkbench
On Slack: mysqlcommunity.slack.com (#workbench)
Report bugs to http://bugs.mysql.com
MySQL documentation can be found here: http://dev.mysql.com/doc/refman/8.0/en/

Options: ReplyQuote


Subject
Views
Written By
Posted
3324
February 17, 2009 04:45PM
Re: schema to a db in mysql administrator
2363
February 18, 2009 02:32AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.