Re: Workbench main objetive?

[Mike Lischke]

Mariano,

you can use your model to create the "physical" database objects (see menu Database -> Forward Engineer) and of course you can share the model file (*.mwb) with your developers. They can load and forward engineer it to have a local copy or use a central server and sync the model with that server, so it stays up to date (sync is a 2-way merge, which sends model changes to the server and reads changed objects from there into your model).

There is no rights management attached to modelling. The privilege system works only on the real db objects. So, it makes sense to have a staging area where your devs can do all the development work and once the structure is final have it merged over to your production box by someone with the proper privs there to do it.

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/