Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Couple of possible solutions, answering because the comments section was getting angry at me.</p> <p>Edit #3 with solution:</p> <p><strong>Apparently E_ERROR and display_errors don't play nicely together</strong></p> <p>You could set error_reporting to E_ALL &amp; ~E_ERROR, and just let your shutdown handler handle the fatal (since it is the last thing that should be called anyhow). </p> <p>Additionally, <code>E_ALL</code> does not encompass <code>E_DEPRECATED</code> prior to PHP 5.4.0, so if you want to catch that too - use <code>~0 &amp; ~E_ERROR</code></p> <hr> <p><strong>display_errors may be bugged</strong></p> <p>Here's a gist on how you can get it to spit out errors even though you told it not to: <a href="https://gist.github.com/1483028" rel="nofollow">https://gist.github.com/1483028</a></p> <p><strong>If you set display_errors to 0 via ini_set() it will still display Fatal Errors</strong></p> <blockquote> <p>Although display_errors may be set at runtime (with ini_set()), it won't have any affect if the script has fatal errors. This is because the desired runtime action does not get executed. </p> </blockquote> <p>Additionally you can send it to stderr as well, so that's awesome.</p> <p><a href="http://www.php.net/manual/en/errorfunc.configuration.php#ini.display-errors" rel="nofollow">http://www.php.net/manual/en/errorfunc.configuration.php#ini.display-errors</a></p> <p>Edit 2: <strong>Make sure you've changed the proper php.ini</strong></p> <p>Just thought of this, and commented as such, but there is more than one php.ini file. If you're doing this on the command line, you'll need to edit the cli one (/etc/php5/cli/php.ini on Ubuntu), and not the web one (/etc/php5/apache2/php.ini)</p> <p>I'd guess you just need to set php.ini to have display_errors 0.</p>
    singulars
    1. This table or related slice is empty.
    1. POPreventing PHP fatal error traceback output when using custom shutdown handler
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USraveren
    1. USCthos
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    1. COYeah -- that's what I was thinking too, but I still get the error output (weird) and that's why I ended up posting the question ... could it be a bug? I wonder ...
      singulars
      1. PO
      1. USrdlowrey
    2. COAnyway, +1 for your time
      singulars
      1. PO
      1. USrdlowrey
    3. COPossibly. Which php.ini are you editing? If you're on ubuntu, there are 2: /etc/php5/cli/php.ini and /etc/php5/apache2/php.ini. If you edited one but not the other.. (But you probably know this, just running through ideas).
      singulars
      1. PO
      1. USCthos
 

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