However, I have noticed that even if you set error reporting to something like E_ERROR or 0, and set the log_threshold to 1. That DB errors are still displayed. To turn off, DB errors you need to change the setting for db_debug within the file ./system/application/config/database.php. This files states this about the setting.

['db_debug'] TRUE/FALSE – Whether database errors should be displayed.

I set db_debug to false, and purposefully created some DB errors. The errors were not displayed on the screen. However, the errors were not logged either, even though I had a setting of 1 for error reporting. I even changed my error reporting threshold to 4, but still no DB Errors were getting written to my log file.

Upon further investigation, I noticed that the query function within the file ./system/application/database/DB_driver.php will only log messages if the db_debug is set to true.

So just be aware of that issue when launching your website into production with db_debug set to false.

CodeIgniter pays no attention to php.ini’s display_errors, which is terrible. In my experience the best way to turn off errors has been to empty the error.php file. Additionally, the function called as to handle errors is named exception_handler. These issues aren’t damning, but difficult to deal with when you really, really don’t want to show errors in production.