Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The root node is not there because you are not using the RecursiveArrayIterator correctly.</p> <p>It's intended use is to have an array with multiple sub-arrays in any level and structure, and give this array into ONE instance of the RecursiveArrayIterator, and to iterate over everything, put this into a RecursiveIteratorIterator.</p> <p>That way, the entire array, including it's top level, will be iterated. </p> <p>Because you abused the RecursiveArrayIterator to be the carrier of information, the top level object is not iterated.</p> <p>Suggested easy example that has some nastyness, but demonstrates the principle:</p> <pre><code>$root = array( 'root_level' ); $block = array( 'first_level' ); $child = array( 'second_level' ); $child_of_child_a = array( 'third_level_a' ); $child_of_child_b = array( 'third_level_b' ); $child[] = $child_of_child_a; $child[] = $child_of_child_b ; $child_of_child_a[] = array(''); $child_of_child_a[] = array(''); $block[] = $child; $root[] = $block ; $storage = new \RecursiveIteratorIterator( new \RecursiveArrayIterator($root), RecursiveIteratorIterator::SELF_FIRST ); var_dump($root); foreach ($storage as $key=&gt;$value) { echo $key.": ".$value."\n"; } </code></pre> <p>Result output:</p> <pre><code>array(2) { [0] =&gt; string(10) "root_level" [1] =&gt; array(2) { [0] =&gt; string(11) "first_level" [1] =&gt; array(3) { [0] =&gt; string(12) "second_level" [1] =&gt; array(1) { ... } [2] =&gt; array(1) { ... } } } } 0: root_level 1: Array 0: first_level 1: Array 0: second_level 1: Array 0: third_level_a 2: Array 0: third_level_b </code></pre> <p>It's output is not quite the same, but my point is that you can iterate over the structure without having every single node to be an instance of the RecursiveArrayIterator. You can add anything that is either an array, or an object acting as an array, or an object that can usefully be iterated.</p>
    singulars
    1. This table or related slice is empty.
    1. PORecursiveIteratorIterator and nested RecursiveArrayIterators
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USSven
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORecursiveIteratorIterator and nested RecursiveArrayIterators
      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. COSeriously, `var_dump($root)` :)?
      singulars
      1. PO
      1. USvee
    2. COThis makes things a little clearer. Thank you. What I really am trying to get to figure out though is the best way to use some of the Spl Iterators to nest Objects in a similar fashion.
      singulars
      1. PO
      1. USwlvrn
 

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