Triggers should not include database name when logging is to the same DB

When I set up logging the DB name is added to the trigger.

This causes a problem when cloning copies of the DB since if the cloned mysql user is able to access the original db, log files will be added to the original DB.

It can be avoided if we check whether we are using the same DB for logging. In this case, we don't need to include the DB name.

This would be a significant pain if the original site was a production site which has been cloned to do development, etc. AND the dev mysql user had access to the prod database since any changes in the dev site would be added to the production logs.