> Are you using 'replicate-wild-do-table = DBName.%' ??

Thanks for the reply.

That's a client-only option, we're not actually having any troubles with
clients ignoring anything in the binary log - the problem I'm describing is
that when a database is not first explictly selected, the master refuses to
write the query to the binary log.

Example 1:

$sql = "insert into database.table values ('somevalue')";
mysql_query($sql);

Query is not written to binary log, so slaves never pick it up.



Example 2:

$sql = "insert into table values ('somevalue')";
// or even "insert into database.table values ('somevalue')";
mysql_select_db("database");
mysql_query($sql);

Query is written to binary log fine, slaves pick it up as long as database
is 'selected'. I can duplicate this issue using the bundled (with mysql)
mysql client by using the '\u database' command, and also not using it, and
I see the same result.

In my original email regarding this I mentioned that if it's by design the
that's fine, from now on we just remember to select the database rather than
referring to it only in the sql string - but I figured it probably isn't by
design and might be worth being looked at.

Regards,
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

Reply via email to