Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><code>require_once</code> and <code>include_once</code> both require that the system keeps a log of what's already been included/required. Every <code>*_once</code> call means checking that log. So there's definitely <em>some</em> extra work being done there but enough to detriment the speed of the whole app?</p> <p>... I really doubt it... Not unless you're on <em>really</em> old hardware or doing it a <em>lot</em>.</p> <p>If you <em>are</em> doing thousands of <code>*_once</code>, you could do the work yourself in a lighter fashion. For simple apps, just making sure you've only included it once <em>should</em> suffice but if you're still getting redefine errors, you could something like this:</p> <pre><code>if (!defined('MyIncludeName')) { require('MyIncludeName'); define('MyIncludeName', 1); } </code></pre> <p>I'll personally stick with the <code>*_once</code> statements but on silly million-pass benchmark, you can see a difference between the two:</p> <pre><code> php hhvm if defined 0.18587779998779 0.046600103378296 require_once 1.2219581604004 3.2908599376678 </code></pre> <p>10-100× slower with <code>require_once</code> and it's curious that <code>require_once</code> is seemingly slower in <code>hhvm</code>. Again, this is only relevant to your code if you're running <code>*_once</code> thousands of times.</p> <hr> <pre><code>&lt;?php // test.php $LIMIT = 1000000; $start = microtime(true); for ($i=0; $i&lt;$LIMIT; $i++) if (!defined('include.php')) { require('include.php'); define('include.php', 1); } $mid = microtime(true); for ($i=0; $i&lt;$LIMIT; $i++) require_once('include.php'); $end = microtime(true); printf("if defined\t%s\nrequire_once\t%s\n", $mid-$start, $end-$mid); </code></pre> <hr> <pre><code>&lt;?php // include.php // do nothing. </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POWhy is require_once so bad to use?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USOli
    1. USOli
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhy is require_once so bad to use?
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI doubt your defined() method is any faster than the built-in lookup table, but I agree with your overall point - surely a non-issue?!
      singulars
      1. PO
      1. USBobby Jack
    2. COI'm fairly sure you're right Bobby but I'm not advocating the defines over _once. It's just an option. The time it would take to interpret the code might even make it marginally slower but, that said, I don't know how thorough the internal method is. It might do extra work to ensure no duplicates.
      singulars
      1. PO
      1. USOli
    3. COThe other downside is APC doesn't cache include_once and require_once calls IIRC
      singulars
      1. PO
      1. USdcousineau
 

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