In direct reference to the accepted answer in this question
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 ...).
Is the above true? It doesn't say this explicitly in the link the answerer provides. And is the only way to mitigate this is to ensure that your application doesn't prefix the schema name to the table refs in queries?
The reason I am asking is because we recently restored from a recent backup after an accidental
drop database. I was also hoping to complete the data by restoring that day's activity from the binlogs. When I extracted the queries from the binlogs I couldn't find a single query before
drop database appeared in the log. - I am also certain that I extracted the correct timestamps.