2 Improved answer
source | link

MySQL doesn't log to the binary log file when you use direct database.table syntax in your update queries (eg. UPDATE Foo.Bar SET ...). My web application never specifies a default database so the data is never logged. I will attempt to use table replication wildcard rules to solve this issue. 

http://dev.mysql.com/doc/refman/5.0/en/replication-rules-db-options.html

I solved the problem my calling mysql_select_db before my INSERT and UPDATE queries.

MySQL doesn't log to the binary log file when you use direct database.table syntax in your update queries (eg. UPDATE Foo.Bar SET ...). My web application never specifies a default database so the data is never logged. I will attempt to use table replication wildcard rules to solve this issue.

http://dev.mysql.com/doc/refman/5.0/en/replication-rules-db-options.html

MySQL doesn't log to the binary log file when you use direct database.table syntax in your update queries (eg. UPDATE Foo.Bar SET ...). My web application never specifies a default database so the data is never logged.  

http://dev.mysql.com/doc/refman/5.0/en/replication-rules-db-options.html

I solved the problem my calling mysql_select_db before my INSERT and UPDATE queries.

1
source | link

MySQL doesn't log to the binary log file when you use direct database.table syntax in your update queries (eg. UPDATE Foo.Bar SET ...). My web application never specifies a default database so the data is never logged. I will attempt to use table replication wildcard rules to solve this issue.

http://dev.mysql.com/doc/refman/5.0/en/replication-rules-db-options.html