Hi,
you haven't mentioned which version you tried, but since you are speaking of the "SQL Editor" tab, it must be WB 5.2, which is in alpha stadium currently.
> am i right to say "MySQL Model" tab is for work in a file not directly
> linked to a real db in the server? actually if it is that will be better,
> i think so i dont need to use forward and backward engineer all the time
Well, WB is primarily a modelling tool and as such is used to design a database, that is, tables, views, stored procedures etc. and their relation to each other. Designing a database doesn't involve the actual data, but rather the meta data. And here is where QB or its incarnation (the SQL Editor in WB) comes into play. This part is all about the data *in* tables. In QB you also could do some design work (managing db objects) but that wasn't its primary task. Now, in WB, this is more strictly separated and certain stuff, which has rarely been used has or will be removed from the SQL Editor part. The design process a such does not need or even involve direct access to a MySQL server. There is some support in the SE to directly access a server, but for the primary task (designing a db) that is not needed. You can easily get the same results by using SQL scripts (dumps).
> when i use the "SQL Editor" tab, its now like query browser right?
Yes.
> but by default when u dbl click a table, u get EDIT table rather than
> a select. why is this so? i am user select is more used than edit,
> which when executed is actually select
The current behavior is mostly that of a design tool yet, not a management tool. Depending on user feedback we might end up with another solution, or even make it configurable, what should happen if the input is that-and-that.
> for db modelling, how do i set a PK to auto_increment?
This hasn't changed much from QB. In the table editor you have a column named AI after each column name of the table under work. It uses a checkbox to switch auto increment.
HTH
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/