MySQL Bugs: #77451: mysql model missing physical schemas tabs

Bug #77451	mysql model missing physical schemas tabs
Submitted:	23 Jun 2015 12:49	Modified:	11 Jun 2018 20:25
Reporter:	mike coutinho	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	6.3.4	OS:	MacOS
Assigned to:		CPU Architecture:	Any
Tags:	model

Description:
In the MySQL Model section, i have several schemas in my file.  The tabs that allow navigation between different schemas are not visible.  The tabs are there as if you blindly click, you can get to each of the different tabs.  The physical labels and tabs are not there though.  See attached file.

How to repeat:
have a model with multiple schemas in it.

worked fine in 6.3.2, broken in 6.3.3 and 6.3.4

view of the missing tabs

Attachment: Screen Shot 2015-06-23 at 8.46.16 AM.png (image/png, text), 20.68 KiB.

schemas

Attachment: multiple_schemas.png (image/png, text), 150.58 KiB.

Thank you for the bug report. I couldn't repeat with a simple model file with multiple schemas (please see attached picture).

MySQL Workbench Community (GPL) for Mac OS X version 6.3.4  revision 0 build 828 (32 bit)
Configuration Directory: /Users/miguel/Library/Application Support/MySQL/Workbench
Data Directory: /Volumes/MySQL Workbench/MySQLWorkbench.app/Contents/Resources
Cairo Version: 1.10.2
OS: OS X 10.10.x Yosemite
CPU: 4x Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz - 16.00GiB RAM

Forgot to ask you for a model file project which presents the issue on your side. Thanks.

if, on my model, i delete the first of the schemas and save my file, the tabs come back when I re-open it.  If i delete any of the other schemas and do the same thing, it does not come back.  It is only the first schema in my model that seems broken, which then breaks the interface. 

Is there a diagnostic tool I can run on the file itself?  Any logs I can look at for error messages?  Can I send in a video of what I am seeing?

If you do a copy and edit the model project so you keep the offended schema and 1 more is repeatable the issue?. If yes provide it as private file. Thanks.

Mike, there *is* a log available via the Help menu. Via Preferences -> Other -> Log Level you can adjust the talkativeness of the logger. See if that gives you any hint about the problem. But a copy of your model would really be the easiest way for us to determine what your problem is.

Thank you for the feedback. Verified with the model test.

Mike, I'm very sorry for the misinformation. The log level option in the preferences are new and not available in a released product yet. At the moment you have to start WB with a command line parameter to set a specific log level. On Mac + Linux this is e.g. "--log-level=debug2" on Win it would be "-log-level=debug2". Available log levels are none, error, warning, info, debug1, debug2 and debug3.

This problem is caused by the sheer size of your model. On the overview page in that first schema tab you have ~1000 objects. For some unknown reasons that leads to problems with drawing the tabs. From what I see we will probably have to rework that part completely, which can take quite a while. In the meantime the best option you have is probably to make your schemas smaller. On a 4K monitor you can make the WB window very large and that also works (if you don't add new objects). Sorry for the inconvienience.

Mike, thanks for the information.  I was just playing with the model today and deleted a bunch of objects in it and the tabs started working again.  I have another 100 objects to move out/delete to help it a little more.  

What tools other than mysql workbench do people use to develop highly complex relationships? 

thank you

i tried various versions of this on the command line and none of them seem to work.  Any thoughts on what I am doing wrong?

computername:Applications mike$ open MySQLWorkbench.app --log-level=debug2
open: unrecognized option `--log-level=debug2'
Usage: open [-e] [-t] [-f] [-W] [-R] [-n] [-g] [-h] [-b <bundle identifier>] [-a <application>] [filenames] [--args arguments]
Help: Open opens files from a shell.
      By default, opens each file using the default application for that file.
      If the file is in the form of a URL, the file will be opened as a URL.
Options:
      -a                Opens with the specified application.
      -b                Opens with the specified application bundle identifier.
      -e                Opens with TextEdit.
      -t                Opens with default text editor.
      -f                Reads input from standard input and opens with TextEdit.
      -F  --fresh       Launches the app fresh, that is, without restoring windows. Saved persistent state is lost, excluding Untitled documents.
      -R, --reveal      Selects in the Finder instead of opening.
      -W, --wait-apps   Blocks until the used applications are closed (even if they were already running).
          --args        All remaining arguments are passed in argv to the application's main() function instead of opened.
      -n, --new         Open a new instance of the application even if one is already running.
      -j, --hide        Launches the app hidden.
      -g, --background  Does not bring the application to the foreground.
      -h, --header      Searches header file locations for headers matching the given filenames, and opens them.

This does launch the app:
computername:Applications mike$ open MySQLWorkbench.app

Search for "osx run app with parameters from terminal". In DuckDuckGo the first hit contains the solution: open MySQLWorkbench.app --args "--log-level=debug3". In the log file you should see something like:

09:07:45 [INF][      WBContext]: Parsing application arguments.
09:07:45 [INF][      WBContext]:     /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
09:07:45 [INF][      WBContext]:     --log-level=debug3
09:07:45 [INF][      WBContext]: Logger set to level 'debug3'
09:07:45 [INF][      Workbench]: Starting up Workbench

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.12 release, and here's the changelog entry:

Tabs separating multiple schemas within the Physical Schemas area of the
MySQL Model tab were not visible.

Thank you for the bug report.