http://solutions.treypiepmeier.com/2008/01/16/mysql-commands-you-should-have-committed-to-memory-already/ So I don't have to figure things out more than once. Tue, 30 Sep 2008 23:40:03 +0000 http://wordpress.org/?v=2.6.2 http://solutions.treypiepmeier.com/2008/01/16/mysql-commands-you-should-have-committed-to-memory-already/#comment-9699 JTJ Thu, 17 Jan 2008 05:38:09 +0000 http://solutions.treypiepmeier.com/2008/01/16/mysql-commands-you-should-have-committed-to-memory-already/#comment-9699 <p>A few things to note:</p> <ol> <li>If your host is localhost, you don't have to do the -h</li> <li>It might be a little safer to just put -p without the password in the command. That way, it'll prompt you for it, and it's not in your history or anything.</li> <li>If you're just doing a backup dump, you can save space by piping your dump through gzip like so: <code>mysqldump -u user -p database_name | gzip > dump_file.sql.gz</code></li> <li>Finally, sometimes there are encoding issues when dumping to a file and importing the dump. Depending on what character encoding your database/tables use, sometimes helps: <code>--default_character-set=latin1 --skip-set-charset</code></li> </ol> A few things to note:

1. If your host is localhost, you don’t have to do the -h
2. It might be a little safer to just put -p without the password in the command. That way, it’ll prompt you for it, and it’s not in your history or anything.
3. If you’re just doing a backup dump, you can save space by piping your dump through gzip like so: mysqldump -u user -p database_name | gzip > dump_file.sql.gz
4. Finally, sometimes there are encoding issues when dumping to a file and importing the dump. Depending on what character encoding your database/tables use, sometimes helps: --default_character-set=latin1 --skip-set-charset

]]>