Hello.
Manual says that --replicate-do-db: " Tells the slave to restrict replication to statements where the default database (that is, the one selected by USE) is db_name." Note that this does not replicate cross-database statements, check what is your default database, when you're running your query. Atle Veka wrote: > More investigation shows that the query does make it to the slave, at > least into the relay log, yet it's still ignored. 'replicate-do-db' is set > and shows the correct DB in the slave status. > > > Atle > - > Flying Crocodile Inc, Unix Systems Administrator > > On Thu, 20 Oct 2005, Atle Veka wrote: > > >>I ran into a problem on a replication setup, where if you issue the >>following CREATE statement on the master the table will get created and >>the query entered into the binlog, however the slave ignores it silently: >> CREATE TABLE `db`.`table` (a INT DEFAULT 0) >> >>I have duplicated this exact issue on several different setups, one >>running 4.0.24 on both the slave and master. Is this by design, is it a >>bug, or? >> >>The manual states >>(http://dev.mysql.com/doc/refman/5.0/en/create-table.html): >>"In MySQL 5.0, the table name can be specified as db_name.tbl_name to >>create the table in a specific database. This works whether or not there >>is a current database. If you use quoted identifiers, quote the database >>and table names separately. For example, `mydb`.`mytbl` is legal, but >>`mydb.mytbl` is not." >> >> >>Atle >>- >>Flying Crocodile Inc, Unix Systems Administrator >> > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
