I'm fairly certain this is a bug. It's on 3.23.46-max and the changelog for .47 doesn't mention it.
I have 2 servers using replication. Server1 is used by client machines and all updates are to it. Server2 stays in perfect sync with it and logs all updates to it's own binary log. I then use mysqlbinlog from server2 to parse out those database changes every half hour or so and send to another server via a (part-time) internet connection where it attempts to maintain a synced copy of the data as well. A "modify table" to add a new field on server1 propogates to server2 but NOT to the third server. I've not tracked down exactly where things are breaking down yet. Server1 and 2 are Linux and are using INNODB tables. Server3 is not Linux and is not able to use INNODB at the moment. Even a "create table ... type=INNODB" works on server3 making the table MyISAM instead. It's just the modify table statements with the addition of a new field that don't make it. I've not captured and analyzed one of the binary logs yet but will try to do so. Just wanted to let someone know of a probable bug. I'll also upgrade to .47 and report back if that resolves this. To reiterate: Server1=Master -> Server2=Slave Replication works fine and everything stays in proper sync. Server2 logs all updates from server1 for a particular database and a PERL script calls mysqlbinlog periodically to capture to plain text all the updates/inserts/deletes. This file is sent to a 3rd server where they're integrated into that copy of the database via the standard command-line mysql client. Any "modify table" statements to add a new field on server1 make it to server2 just fine but NOT to the 3rd server. --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
