Comments on: MySQL command line vs. visual editors – reflections https://shlomi-noach.github.io/blog/mysql/mysql-command-line-vs-visual-editors-reflections Blog by Shlomi Noach Wed, 01 Feb 2012 20:47:51 +0000 hourly 1 https://wordpress.org/?v=5.3.3 By: Gerry https://shlomi-noach.github.io/blog/mysql/mysql-command-line-vs-visual-editors-reflections/comment-page-1#comment-68205 Wed, 01 Feb 2012 20:47:51 +0000 https://shlomi-noach.github.io/blog/?p=4647#comment-68205 I favor the CLI, although I use Workbench side-by-side, but not for admin tasks.

For example, if you only enable root@localhost to have GRANT OPTION (or replace with the administrative permission of your choice), it’s not always easy or convenient to do port tunneling so you can use a GUI. OTH, the MySQL CLI utility will always be there on the server.

My $.02
G

]]> By: Sheeri Cabral https://shlomi-noach.github.io/blog/mysql/mysql-command-line-vs-visual-editors-reflections/comment-page-1#comment-68167 Wed, 01 Feb 2012 15:42:09 +0000 https://shlomi-noach.github.io/blog/?p=4647#comment-68167 While I agree with you that the commandline is the ultimate tool, many times the extra layer(s) of abstraction help a developer get familiar with the MySQL environment and how queries actually work in MySQL, without having to learn a new tool also.

There is value in exposing a little bit of MySQL at a time.

I use a separate editor for when I’m creating stored procedures or events, long pieces of code that I likely will troubleshoot for a while before getting it right.

]]> By: Giuseppe Maxia https://shlomi-noach.github.io/blog/mysql/mysql-command-line-vs-visual-editors-reflections/comment-page-1#comment-68094 Wed, 01 Feb 2012 12:11:13 +0000 https://shlomi-noach.github.io/blog/?p=4647#comment-68094 Being a Unix user, one of the reasons for using MySQL command line tools rather than GUIs is that with the CLi you can easily integrate other shell tools with MySQL input or output.
Admittedly, I am a proficient command line user, and therefore for me it is relatively easy to run a shell loop using input from the MySQL CLI tool and push back the output to MySQL, all in the same line.
Like this:
$ for T in $(mysql -B -N -e ‘show
tables from world’) ; do echo “CREATE TABLE world2.$T LIKE world.$T;” ; done | mysql -vv

I understand that someone used to a GUI may look at that as an abomination, but for me this is one of the simplest uses of the MySQL CLI integrated to shell tools. There are more complex, and more powerful things that can be done, and I feel very much satisfied with the command line for this reason. I would be lost in a GUI, which is in many cases very limiting for me.

When is a GUI helpful? When you have to create queries from a complex schema and you need an enhanced editor that suggests you table and column names efficiently. I use Aqua Data Studio for this reason only.

]]>