| StuBo | its just in case you don't :) |
| chadmaynard | oh ok. I'll RTFM |
| StuBo | ok chadmaynard: thansk for that, I know what you mean about the -ppassword thing then I guess I zip and tar up my hotcopied files afterwards ? tar -czf mydb.tar.gz mydb |
| chadmaynard | yah you could and the -pPASSWORD thing applies to all mysql-related binaries i can think of mysql, mysqldump, mysqlhotcopy, etc |
| StuBo | has it always been like that ? Im sure last time I did a hotcopy I had it -p password with the space this was on mysql 4.something |
| chadmaynard | nope its always been -pPassword |
| StuBo | yep well, its working anyhow |
| chadmaynard | !man41 mysqlhotcopy |
| the_wench | see http://dev.mysql.com/doc/refman/4.1/en/client-utility-overview.html |
| chadmaynard | see |
| StuBo | so this hotcopy... |
| chadmaynard | theres the 3.23, 4.0, 4.1 manpage |
| StuBo | does it lock all tables at once, or one at a time as its copying them? |
| chadmaynard | all of them at once IIRC |
| StuBo | so theres no change of inconsistancy in the db like someone editing the last table...as its going through them |
| chadmaynard | sure. If you say so |
| jbalint | yes, thats sensib;e |
| StuBo | is it true though? :) |
| jbalint | presumablt |
| chadmaynard | we don't know, but thats a good reason! |
| jbalint | s/t/y |
| StuBo | it would be a good reason to lock all tables |
| chadmaynard | my guess is it was easiest. hehe |
| StuBo | would be silly to lock opne at a time....but I think it locks em one at a time |
| jbalint | well, without transactions, it makes the most sense |
| StuBo | myisam |
| jbalint | right |
| StuBo | hotcopy is just for myisam...so Im guessing it could lock em one table at a time |
| jbalint | could, but as you said..... |