syd3:/mysql/var# ../bin/mysqlbinlog syd3-bin.001
# at 4
#010926 17:41:57 server id 1 Start: binlog v 1, server v 3.23.42-log
created 010926 17:41:57
# at 73
#010926 17:48:11 server id 1 Query thread_id=1119 exec_time=0
error_code=0
use agn_users;
SET TIMESTAMP=1001490491;
CREATE TABLE `fred` (`mum` INT DEFAULT '1' not null AUTO_INCREMENT , PRIMARY
KEY (`mum`));
Create table is logged to binlog - but alter table to add a new column is
not. Alter table to drop that new column, IS logged.
How come? Has anyone else seen behaviour with replication where only some
queries are logged and not others?
----- Original Message -----
From: "Jason Brooke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, September 25, 2001 7:17 PM
Subject: replication
> Why, when doing replication, would some queries to a replicated database
get
> logged to the binlog, but not others? Is replication still very beta, or
is
> it considered to be stable now?
>
> The slave of course falls behind because of the queries that don't go to
the
> binlog
>
> versions 3.23.42 and 3.23.41, and/or mixtures of them both
>
> jason
---------------------------------------------------------------------
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
