Are there any reports/logs saying all PHP and MySQL errors that occured on server? With date, time, some user info (browser, IP), and count of that error happened if possible.
In addition every time my mysql_query fails die message is pulled from included file:
$error_message[0] = 'Error no. 0!';
$error_message[1] = 'Error no. 1!';
$error_message[2] = 'Error no. 2!';
Is there a way to monitor which message and when was displayed?
Yes, there are error logs for both: httpd (or apache) and mysqld.
You find them in:
/var/log/httpd/error_log
/var/log/mysqld.log
(these path could be a little different on your sever depends on configuration files, eg. you can specify mysql error log file location passing --log-error=XXX option to mysqld)
You can do it by sticking to exceptions instead of "die()" calls, and by catching them, then logging.
Good solution for that is eg. Sentry - it saves information in the way you require (time of occurrence, details, number of occurences, logger/category, level etc.).
Look in /var/logs/apache/ or /var/logs/httpd/ if it's a Linux / UNIX server.
"Is there a way to monitor which message and when was displayed?"
This is not about the main question, however if you're worried about exposed error messages, you can simply disable showing errors in PHP, which actually means you would not have MySQL errors showing to the visitors also (You're working on MySQL via PHP, if you're talking about a web application)
That might help! :)
Do you think try, catch would works then? you just need to use it everywhere in order to catch all the possible errors.
You may also make your own MySQL adapter class and then wrap the original functions inside the try, catch block. That would make it easier if you could apply that on your code, but for PHP errors, still need to cover fatal-error-possible parts, e.g. working on file system, with try, catch blocks manually.
When you're gonna log them on the database or file system, obviously you can log the date and time also.
Note: you may consider the overhead also! you can benchmark to see how much your code would be slower after using try, catch blocks.
mysql_query() || die()should only be for initial development. Once you've got it working, you should instead raise an typed exception, and try to plan for, and catch, pretty much everything.