MySQL cli does not remember history of some commands
up vote
0
down vote
favorite
I use linux OS with mysql database.
mysql CLI doesn't log some commands in ~/.mysql_history .
For example can not log create user.
How can force cli to store all commands in mysql_history ?
How can fix this problem ?
mysql mariadb
edited Nov 18 at 12:57
Dave M
4,30972428
asked Nov 18 at 10:20
mah454
1071
add a comment |
up vote
0
down vote
favorite
I use linux OS with mysql database.
mysql CLI doesn't log some commands in ~/.mysql_history .
For example can not log create user.
How can force cli to store all commands in mysql_history ?
How can fix this problem ?
mysql mariadb
edited Nov 18 at 12:57
Dave M
4,30972428
asked Nov 18 at 10:20
mah454
1071
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I use linux OS with mysql database.
mysql CLI doesn't log some commands in ~/.mysql_history .
For example can not log create user.
How can force cli to store all commands in mysql_history ?
How can fix this problem ?
mysql mariadb
edited Nov 18 at 12:57
Dave M
4,30972428
asked Nov 18 at 10:20
mah454
1071
I use linux OS with mysql database.
mysql CLI doesn't log some commands in ~/.mysql_history .
For example can not log create user.
How can force cli to store all commands in mysql_history ?
How can fix this problem ?
mysql mariadb
mysql mariadb
edited Nov 18 at 12:57
Dave M
4,30972428
asked Nov 18 at 10:20
mah454
1071
edited Nov 18 at 12:57
Dave M
4,30972428
asked Nov 18 at 10:20
mah454
1071
edited Nov 18 at 12:57
Dave M
4,30972428
edited Nov 18 at 12:57
Dave M
4,30972428
edited Nov 18 at 12:57
Dave M
4,30972428
4,30972428
asked Nov 18 at 10:20
mah454
1071
asked Nov 18 at 10:20
mah454
1071
asked Nov 18 at 10:20
mah454
1071
1071
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
12
down vote
That behaviour is by design, which as far as I know you can not override.
By default all interactive statements are logged, including the CREATE USER statement, except when they contain password information.
Although you can add extra conditions that will prevent logging certain additional statements (set either the --histignore option or the MYSQL_HISTIGNORE environment variable) or completely stop logging with for instance the --batch switch, logging passwords is as far as I know not possible.
https://dev.mysql.com/doc/refman/5.7/en/mysql-logging.html
mysql ignores for logging purposes statements that match any pattern in the “ignore” list. By default, the pattern list is
"*IDENTIFIED*:*PASSWORD*", to ignore statements that refer to passwords.
answered Nov 18 at 13:43
HBruijn
52.4k1087143
1
Whether possible or not, it's certainly not desirable.
– jpmc26
Nov 19 at 4:29
add a comment |
up vote
1
down vote
Try to:
set MYSQL_HISTFILE environment variable explicitily
touch .mysql_history
chmod 600 .mysql_history
History in not written immediately, but when you exit the client.
answered Nov 18 at 11:15
Nicola Ben
1214
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
12
down vote
That behaviour is by design, which as far as I know you can not override.
By default all interactive statements are logged, including the CREATE USER statement, except when they contain password information.
Although you can add extra conditions that will prevent logging certain additional statements (set either the --histignore option or the MYSQL_HISTIGNORE environment variable) or completely stop logging with for instance the --batch switch, logging passwords is as far as I know not possible.
https://dev.mysql.com/doc/refman/5.7/en/mysql-logging.html
mysql ignores for logging purposes statements that match any pattern in the “ignore” list. By default, the pattern list is
"*IDENTIFIED*:*PASSWORD*", to ignore statements that refer to passwords.
answered Nov 18 at 13:43
HBruijn
52.4k1087143
1
Whether possible or not, it's certainly not desirable.
– jpmc26
Nov 19 at 4:29
add a comment |
up vote
12
down vote
That behaviour is by design, which as far as I know you can not override.
By default all interactive statements are logged, including the CREATE USER statement, except when they contain password information.
Although you can add extra conditions that will prevent logging certain additional statements (set either the --histignore option or the MYSQL_HISTIGNORE environment variable) or completely stop logging with for instance the --batch switch, logging passwords is as far as I know not possible.
https://dev.mysql.com/doc/refman/5.7/en/mysql-logging.html
mysql ignores for logging purposes statements that match any pattern in the “ignore” list. By default, the pattern list is
"*IDENTIFIED*:*PASSWORD*", to ignore statements that refer to passwords.
answered Nov 18 at 13:43
HBruijn
52.4k1087143
1
Whether possible or not, it's certainly not desirable.
– jpmc26
Nov 19 at 4:29
add a comment |
up vote
12
down vote
up vote
12
down vote
That behaviour is by design, which as far as I know you can not override.
By default all interactive statements are logged, including the CREATE USER statement, except when they contain password information.
Although you can add extra conditions that will prevent logging certain additional statements (set either the --histignore option or the MYSQL_HISTIGNORE environment variable) or completely stop logging with for instance the --batch switch, logging passwords is as far as I know not possible.
https://dev.mysql.com/doc/refman/5.7/en/mysql-logging.html
mysql ignores for logging purposes statements that match any pattern in the “ignore” list. By default, the pattern list is
"*IDENTIFIED*:*PASSWORD*", to ignore statements that refer to passwords.
answered Nov 18 at 13:43
HBruijn
52.4k1087143
That behaviour is by design, which as far as I know you can not override.
By default all interactive statements are logged, including the CREATE USER statement, except when they contain password information.
Although you can add extra conditions that will prevent logging certain additional statements (set either the --histignore option or the MYSQL_HISTIGNORE environment variable) or completely stop logging with for instance the --batch switch, logging passwords is as far as I know not possible.
https://dev.mysql.com/doc/refman/5.7/en/mysql-logging.html
mysql ignores for logging purposes statements that match any pattern in the “ignore” list. By default, the pattern list is
"*IDENTIFIED*:*PASSWORD*", to ignore statements that refer to passwords.
answered Nov 18 at 13:43
HBruijn
52.4k1087143
answered Nov 18 at 13:43
HBruijn
52.4k1087143
answered Nov 18 at 13:43
HBruijn
52.4k1087143
answered Nov 18 at 13:43
HBruijn
52.4k1087143
52.4k1087143
1
Whether possible or not, it's certainly not desirable.
– jpmc26
Nov 19 at 4:29
add a comment |
1
Whether possible or not, it's certainly not desirable.
– jpmc26
Nov 19 at 4:29
1
1
Whether possible or not, it's certainly not desirable.
– jpmc26
Nov 19 at 4:29
Whether possible or not, it's certainly not desirable.
– jpmc26
Nov 19 at 4:29
add a comment |
up vote
1
down vote
Try to:
set MYSQL_HISTFILE environment variable explicitily
touch .mysql_history
chmod 600 .mysql_history
History in not written immediately, but when you exit the client.
answered Nov 18 at 11:15
Nicola Ben
1214
add a comment |
up vote
1
down vote
Try to:
set MYSQL_HISTFILE environment variable explicitily
touch .mysql_history
chmod 600 .mysql_history
History in not written immediately, but when you exit the client.
answered Nov 18 at 11:15
Nicola Ben
1214
add a comment |
up vote
1
down vote
up vote
1
down vote
Try to:
set MYSQL_HISTFILE environment variable explicitily
touch .mysql_history
chmod 600 .mysql_history
History in not written immediately, but when you exit the client.
answered Nov 18 at 11:15
Nicola Ben
1214
Try to:
set MYSQL_HISTFILE environment variable explicitily
touch .mysql_history
chmod 600 .mysql_history
History in not written immediately, but when you exit the client.
answered Nov 18 at 11:15
Nicola Ben
1214
answered Nov 18 at 11:15
Nicola Ben
1214
answered Nov 18 at 11:15
Nicola Ben
1214
answered Nov 18 at 11:15
Nicola Ben
1214
1214
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f940571%2fmysql-cli-does-not-remember-history-of-some-commands%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
