Exactement ce que je cherchais

You can use the mysql_config_editor utility to store authentication credentials in an encrypted login path file named .mylogin.cnf.

To create a new set of credentials run:

mysql_config_editor set --host=db.host.org --user=dbuser --password

and enter your password when prompted.

This will store your authentication credentials in the default client login path.

You can store multiple authentication credentials by specifying a different --login-path option:

mysql_config_editor set --login-path=db2 --host=db2.host.org --user=dbuser --password

By default, the mysql client reads the [client] and [mysql] groups from other option files, so it reads them from the login path file as well. With a --login-path option, client programs additionally read the named login path from the login path file. The option groups read from other option files remain the same. Consider this command:

mysql --login-path=db2

The mysql client reads [client] and [mysql] from other option files, and [client], [mysql], and [mypath] from the login path file.

To print out all the information stored in the configuration file run:

mysql_config_editor print --all=true

More information about the utility can be found at "mysql_config_editor — MySQL Configuration Utility".

Use ` instead of ' in the database name, and escape the _

GRANT ALL PRIVILEGES ON xian\_%.* TO xian@'192.168.1.%';

Pour un cluster Aurora donné, 3 endpoints :

• cluster endpoint : pointe toujours sur le master
• reader endpoint : pointe toujours sur un slave
• instance endpoint : permet de pointer spécifiquement une instance donnée. Ne garantit pas que cette instance restera un slave ou un master.

You can determine which DB instance in an Aurora DB cluster that a connection is connected to by checking the innodb_read_only global variable, as shown in the following example.
SHOW GLOBAL VARIABLES LIKE 'innodb_read_only';
The innodb_read_only variable will be set to ON if you are connected to an Aurora Replica and OFF if you are connected to the primary instance.

mysql -N -e 'show databases' | while read dbname; do mysqldump --complete-insert --routines --triggers --single-transaction "$dbname" > "$dbname".sql; done

todo : regarder les options

via skunnyk

Dans l'idéal il ne faudrait pas utiliser les paramètres par défauts et lire 100 de la doc pour faire sa propre conf... dans l'idéal.

via sebsauvage

Chapter 17 de la doc MySQL : toread

nouveau protocole de replication mysql

via Skunnyk

Point de vue différents :)

Ici, lorsqu'on utilise "localhost", la connexion va se faire par une socket et lorsqu'on utilise "127.0.0.1", la connexion se fera par tcp. On pourrait se dire que le comportement est anormal, mais en fait, non :

"The patch won't be added as then "localhost" has two meanings - one time meaning "use the unixdomain socket in the default location" and one time actually "resolve localhost and use TCP" as it is taught in many places that "localhost" in MySQL has the first meaning we keep it there."

La socket est déterminée ici dans le php.ini :
; Default socket name for local MySQL connects. If empty, uses the built-in
; MySQL defaults.
mysql.default_socket =

Je me garde ça au chaud, ça peut servir

Todo sur mon dump pour ne plus avoir le warning

Comment mettre en place un slave qui réplique avec percona

Script pour backup toutes ses bases dans des fichiers séparés