of whether it is for MyISAM or
> InnoDB, will come through during a mysqldump.
>
>
> ------
>
> *From:* Mark Maunder [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, August 05, 2008 12:17 PM
> *To:* Rolando Edwards
> *Cc:* mysql@lists.mysql.com
>
h during a mysqldump.
From: Mark Maunder [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 05, 2008 12:17 PM
To: Rolando Edwards
Cc: mysql@lists.mysql.com
Subject: Re: Possible bug in mysqldump?
Thanks for the reply Rolando.
In both the examples I provided (pipe and t
se --master-data in the mysqldump
>
> 5) In mysql session 2, run "CHANGE MASTER TO MASTER_LOG_FILE=' from SHOW MASTER STATUS>,MASTER_LOG_POS=' STATUS>';"
>
> 6) In mysql session 2,run 'START SLAVE'.
>
> 7) In mysql session 1, run 'UNLOCK TA
5) In mysql session 2, run "CHANGE MASTER TO MASTER_LOG_FILE=',MASTER_LOG_POS='';"
6) In mysql session 2,run 'START SLAVE'.
7) In mysql session 1, run 'UNLOCK TABLES'
Give it a try !!!
-Original Message-
From: Mark Maunder [mailto:[EMAIL PROTECTED]
Se
Hi all,
I'm busy setting up replication and have encountered what looks like a bug
in mysqldump. The following commands work perfectly:
Running the following commands in the mysql client on the slave:
stop slave;
reset slave;
create database dbName;
CHANGE MASTER TO MASTER_HOST='masterHost', MAST
I have been running into problems with mysqldump. I have not been able to figure out
why mysqldump isnt working as I hope it would. Anyway I thought I'll make the
mysql-list aware of the problem and hopefully it will help someone. Or better yet
someone knows what I am doing wrong and could point
I just noticed that mysqldump -d outputs
/*!4 ALTER TABLE equity_ind1 DISABLE KEYS */;
at the end of the dump of the table def...
If I understand this correctly... this will be executed
by any version of mysql version 4 and up...
That would be fine, except that since it is not dumping
