Databases
StackOverflow2013
Postsdbo
POCatch a fatal exception and continue
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCatch a fatal exception and continue
    primarykey
    data
    text
    <p>I know, that by its very definition, a fatal exception is supposed to kill the execution, and should not be suppressed, but here's the issue.</p> <p>I'm running a script that scrapes, parses and stores in a DB about 10,000 pages. This takes a couple of hours, and in rare cases (1 in 1000) a page fails parsing and throws a fatal exception.</p> <p>Currently, I'm doing this:</p> <pre><code>for ($i=0;$i&lt;$count;$i++) { $classObject = $classObjects[$i]; echo $i . " : " . memory_get_usage(true) . "\n"; $classDOM = $scraper-&gt;scrapeClassInfo($classObject,$termMap,$subjectMap); $class = $parser-&gt;parseClassInfo($classDOM); $dbmanager-&gt;storeClassInfo($class); unset($classDOM,$class,$classObject); } </code></pre> <p>Can I do something like</p> <pre><code>for ($i=0;$i&lt;$count;$i++) { $classObject = $classObjects[$i]; echo $i . " : " . memory_get_usage(true) . "\n"; try { $classDOM = $scraper-&gt;scrapeClassInfo($classObject,$termMap,$subjectMap); $class = $parser-&gt;parseClassInfo($classDOM); $dbmanager-&gt;storeClassInfo($class); unset($classDOM,$class,$classObject); } catch (Exception $e) { //log the error here continue; } } </code></pre> <p>The code above doesn't work for <code>fatal exceptions</code>.</p> <p>Would it be possible to do something like this: If I moved the main loop into a method, and then call the method from <code>register_shutdown_function</code> ?</p> <p>Like this:</p> <pre><code>function do($start) { for($i=$start;$i&lt;$count;$i++) { //do stuff here } } register_shutdown_function('shutdown'); function shutdown() { do(); } </code></pre> <p>This is the message that is output when execution stops:</p> <pre><code>Fatal error: Call to a member function find() on a non-object in ... </code></pre> <p>I expect this above message when a page isn't parse-able by the method I am using. I'm fine with just skipping that page and moving on to the next iteration of the loop.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USxbonez
    1. USxbonez
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCatch a fatal exception and continue
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCatch a fatal exception and continue
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCatch a fatal exception and continue
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat is a `fatal exception`? How is your `catch (Exception $e)` not working?
      singulars
      1. POCatch a fatal exception and continue
      1. USCharles Sprayberry
    2. COIndeed..... Is someone throwing something that doesn't extend `Exception`?
      singulars
      1. POCatch a fatal exception and continue
      1. USWrikken
    3. CO...in which case, can't you just do `} catch ($e) {`?
      singulars
      1. POCatch a fatal exception and continue
      1. USDaveRandom
 

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