Databases
StackOverflow2013
Postsdbo
POHow to log database errors in zend framework
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to log database errors in zend framework
    primarykey
    data
    text
    <p>I am using zend framework 1.12 for my project. I want to catch all types of fatal errors and send them to an email address for quick fix. I have written the below mentioned code in Bootstrap.php file for this purpose.</p> <pre><code>protected function _initFatalErrorCatcher() { register_shutdown_function(array($this, 'errorlogHandler')); } public function errorlogHandler() { $e = error_get_last(); if (!is_null($e)) { //fatal error $msg = 'Fatal error: ' . $e['message']; $msg .= ' in' . $e['file']; $msg .= ' on line: ' . $e['line']; $mail = new Zend_Mail('utf-8'); $mail-&gt;setBodyHtml($msg); $mail-&gt;setFrom('zzz@z.com'); $mail-&gt;addTo('yyy@y.com'); $mail-&gt;setSubject('check this error'); $mail-&gt;send(); } } </code></pre> <p>Using the above code, i am able to send fatal errors other than database connection related errors and query related errors to email. I followed the instructions from <a href="https://stackoverflow.com/questions/4345274/catch-zend-pdo-exception">Catch Zend PDO Exception</a> as well, but i believe i am missing something as its not working.</p> <p>Any help on this will be appreciated.</p> <p><strong>EDIT:</strong></p> <p>I am also using Zend_Log to write the error logs in a log-file. But, using this i could not find a way to write the fatal errors. Code for this is given below.</p> <pre><code>$writer = new Zend_Log_Writer_Stream(APPLICATION_PATH . "/../data/log-file.log"); $errors = $this-&gt;_getParam('error_handler'); $exception = $errors-&gt;exception; $log = new Zend_Log($writer); $log-&gt;debug($exception-&gt;getMessage() . "\n" . $exception-&gt;getTraceAsString()); </code></pre> <p><strong>Scenario for database connection related issue:</strong></p> <p>If there is any error in host name, database name or in user name, it shows a Fatal error in browser like below. But its not detected by register_shutdown_function() or Zend_Log().</p> <pre><code>Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[42000] [1044] Access denied for user 'AAAA'@'%' to database 'BBBB'' in /var/www/project_name/library/Zend/Db/Adapter/Pdo/Abstract.php on line 144 PDOException: SQLSTATE[42000] [1044] Access denied for user 'AAAA'@'%' to database 'BBBB' in /var/www/project_name/library/Zend/Db/Adapter/Pdo/Abstract.php on line 129 </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USDebashis
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to log database errors in zend framework
      1. USsdespont
      1. VTFavorite
    1. COLook into Zend_Log
      singulars
      1. POHow to log database errors in zend framework
      1. USOrangepill
    2. COI already used that but using Zend_Log i didn't find a way to to list the fatal errors. Please check my edit part in the above post for details.
      singulars
      1. POHow to log database errors in zend framework
      1. USDebashis
    3. CODo you have an example of a type of error that this is failing on... really hard errors (like syntax errors) are not going to be resolvable by any means, at least that I'm aware of.
      singulars
      1. POHow to log database errors in zend framework
      1. USOrangepill
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload