Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Example usage of <a href="http://php.net/manual/class.recursivearrayiterator.php" rel="nofollow">RecursiveArrayIterator</a></p> <pre><code>$array = array( 0 =&gt; 'a', 1 =&gt; array('subA','subB',array(0 =&gt; 'subsubA', 1 =&gt; 'subsubB', 2 =&gt; array(0 =&gt; 'deepA', 1 =&gt; 'deepB'))), 2 =&gt; 'b', 3 =&gt; array('subA','subB','subC'), 4 =&gt; 'c' ); foreach (return new RecursiveIteratorIterator(new RecursiveArrayIterator($array)) as $key =&gt; $val) { printf( '%s: %s' . "\n", $key, $val ); } /* Output: 0: a 0: subA 1: subB 0: subsubA 1: subsubB 0: deepA 1: deepB 2: b 0: subA 1: subB 2: subC 4: c */ </code></pre> <hr> <p>extending <code>RecursiveIteratorIterator</code> to return the current key-stack</p> <pre><code>class MyRecursiveIteratorIterator extends RecursiveIteratorIterator { public function key() { return json_encode($this-&gt;getKeyStack()); } public function getKeyStack() { $result = array(); for ($depth = 0, $lim = $this-&gt;getDepth(); $depth &lt; $lim; $depth += 1) { $result[] = $this-&gt;getSubIterator($depth)-&gt;key(); } $result[] = parent::key(); return $result; } } foreach ($it = new MyRecursiveIteratorIterator(new RecursiveArrayIterator($array)) as $key =&gt; $val) { printf('%s (%s): %s' . "\n", implode('.', $it-&gt;getKeyStack()), $key, $val); } /* Output: 0 ([0]): a 1.0 ([1,0]): subA 1.1 ([1,1]): subB 1.2.0 ([1,2,0]): subsubA 1.2.1 ([1,2,1]): subsubB 1.2.2.0 ([1,2,2,0]): deepA 1.2.2.1 ([1,2,2,1]): deepB 2 ([2]): b 3.0 ([3,0]): subA 3.1 ([3,1]): subB 3.2 ([3,2]): subC 4 ([4]): c */ </code></pre> <hr> <p>Yet another version, using no RecursiveArrayIterator this time:</p> <pre><code>function flatten(array $array = array(), $keyStack = array(), $result = array()) { foreach ($array as $key =&gt; $value) { $keyStack[] = $key; if (is_array($value)) { $result = flatten($value, $keyStack, $result); } else { $result[] = array( 'keys' =&gt; $keyStack, 'value' =&gt; $value ); } array_pop($keyStack); } return $result; } foreach (flatten($array) as $element) { printf( '%s: %s (depth: %s)' . "\n", implode('.', $element['keys']), $element['value'], sizeof($element['keys']) ); } /* 0: a (depth: 1) 1.0: subA (depth: 2) 1.1: subB (depth: 2) 1.2.0: subsubA (depth: 3) 1.2.1: subsubB (depth: 3) 1.2.2.0: deepA (depth: 4) 1.2.2.1: deepB (depth: 4) 2: b (depth: 1) 3.0: subA (depth: 2) 3.1: subB (depth: 2) 3.2: subC (depth: 2) 4: c (depth: 1) */ </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POTransparently flatten an array
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBo A
    1. USYoshi
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTransparently flatten an array
      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. COUgly?? I was surprised of it's beauty. :(
      singulars
      1. PO
      1. USYoshi
    2. CO@stereofrog `array_walk_recursive($array, function($v, $k) { echo "$k => $v\n"; });` achieves the same as the first one. Note that both approaches cannot create a new array while maintaining keys. Returning a flattened array is only possible when forsaking keys.
      singulars
      1. PO
      1. USGordon
    3. COI think the second variant should return an array as key (not imploded), so it's always clear what the concrete subkeys are.
      singulars
      1. PO
      1. UShakre
 

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