Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think you cannot achieve what you're saying with the default error controller generated from <code>zf create project</code> because the lines involved are these</p> <pre><code>// Log exception, if logger available if ($log = $this-&gt;getLog()) { $log-&gt;log($this-&gt;view-&gt;message, $priority, $errors-&gt;exception); $log-&gt;log('Request Parameters', $priority, $errors-&gt;request-&gt;getParams()); } </code></pre> <p>i.e. the default error controller only log the message, the priority and the exception and the firebug writer format them in the way you shown.</p> <p>To achieve what you're saying you should hack the <code>Zend_Log_Writer_Firebug</code> class to display the stacktrace using the firebug console or alternatively you can play with a custom formatter class added to your logger.</p> <p>I did something similar by creating a mail logger which displays formatted exception stacktrace in a mail message and use when in production to obtain a formatted log of the exception sent by email. You can find it <a href="https://github.com/fabn/zle/tree/develop/library/Zle/Log" rel="nofollow">here on Github</a> and <a href="http://www.codewithstyle.eu/2011/01/26/zend-framework-exception-notifier/" rel="nofollow">here</a> you can find its usage.</p> <p>Moreover you can see an example on how to use the firebug console using the ZF classes in the <a href="http://framework.zend.com/svn/framework/standard/trunk/library/Zend/Db/Profiler/Firebug.php" rel="nofollow"><code>Zend_Db_Profiler_Firebug</code></a> class.</p> <p>So to answer your question, no you can't do that without writing some custom class and it as writer or formatter to the log object nor you can do that by just using the <code>application.ini</code> file.</p>
    singulars
    1. This table or related slice is empty.
    1. POFirePHP does not show extras when used with Zend_Log_Writer_Firebug
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USFabio
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POFirePHP does not show extras when used with Zend_Log_Writer_Firebug
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for your thoughts - I actually can edit the Error-Controller and could add the extra-information of the log to the first parameter - but then I won't get the wanted functionality of expanding or collapsing entries. I played around with the Formatter as well and I may be able to get the result I want by enhancing the Logger-class. However, I feel that the Zend_Log_Writer_Firebug should use the possibility of FirePHP/FireBug be default.
      singulars
      1. PO
      1. USLars
 

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