Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It only takes a minute to sign up.
Sign up to join this community
I am just starting to use MySQL Workbench 6.3, and I want to just run simple queries. I've created a table with the appropriate schema and everything, but I can't seem to observe the output from my script. Here's what it looks like:
I click on "run script file" in the Scripting drop down menu, but it doesn't seem to do anything at all? Even if there's a syntax error, I'd like to just see the output and debug my script. Am I missing something obvious?
Are there any records in table_A (not a good name by the way)? It should at least give you field names though.
For problems like this, it's always best to go back to the good-ol CLI (Command Line Interface) to make sure that nothing's wrong somewhere.
You could also open a new Query (interactive) window and copy, paste and run your code and check that way.
As @MikeLischke points out, the system wasn't designed for interactive scripting in modelling mode (unsurprising really).
However, when you open up MySQL Workbench, you have to choose the modelling option. You then get a new tab with that functionality. You can also open a new Query tab (File-> New Query tab...). You have to connect to an (already existing) schema to actually run any SQL (logically enough).
In the interests of fairness, I think you could maybe mark Mike's post as the correct answer (and give me a +1 if you think I deserve it! :-) ).
insert the values myself in the script/query.
– Sother
Mar 4 '16 at 5:49
(Open) New Query. All I see is Open Model, and this doesn't allow me to write any Queries.
– Sother
Mar 4 '16 at 6:10
MySQLWorkbench consists of 2 major parts:
The first one is what you would use to run queries against an existing server, do maintenance (e.g. administer users + privileges or do backups). The second one is for designing a database. In modeling you don't work with actual data, only with meta data (db structure, db objects, user data types, relationships, documentation etc.). Scripts you add to a model therefore cannot be run standalone. They are used when you forward engineer your model to a physical server (creating so a real db from your model).
