Earlier this week we had a discussion with fellow DBAs about our mysql prompts, and at the end of the day it showed up, that a lot of us hit the same problem.<\/p>\n
The problem is, that when you set up your mysql prompt then \u2018\\h\u2019 will be resolved to \u2018localhost\u2019 when you connect locally \u2013 instead the name of your host as you expect it. It always bugs me, and once I spent a good afternoon figuring out how to workaround this.<\/p>\n
Well, the workaround is not a big deal, because you can insert any text into your mysql prompt, and after you realise that you can do it, then it is easy: just put the hostname into your prompt with your chosen provisioning tool and that will do.<\/p>\n
<\/p>\n
For example in my puppet installations I use the following setting in the template file from I generate the \/etc\/my.cnf file:<\/p>\n
It says: \u201cusername@hostname (connected_host) [database_name]\u201d which is really informative. Let me show you this on live servers!<\/p>\n You can see that looking at this prompt I am able to say that which username I used, which host I am running the mysql command, what server will I run my commands and in which database I am.<\/p>\n There is also one more thing I want to show you, and that is colorising!<\/p>\nprompt = \"\\u@<%= @fqdn %> (\\h) [\\d]> \"<\/code><\/p>\n[banyek@db-dev.bfc \/home\/banyek]# mysql -s
\nbanyek@db-dev.bfc.kinja-ops.com (localhost) [(none)]> \\q
\n[banyek@db-dev.bfc \/home\/banyek]# mysql -s -h db-dev.xyz.kinja-ops.com
\nbanyek@db-dev.bfc.kinja-ops.com (db-dev.xyz.kinja-ops.com) [(none)]> \\q
\n[banyek@db-dev.bfc \/home\/banyek]#<\/code><\/p>\n