Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you add a <code>use strict</code> to your script you'll get the fatal error <em>Can't use string ("1") as a HASH ref while "strict refs" in use at [the call to <code>merge_hash_refs</code>]</em>. It appears that the closures created by the <code>&lt;defer&gt;</code> directives are causing the contents of <code>@item</code> to be the ones when the production matched instead of the hashrefs eventually returned by the subrules. Removing the <code>&lt;defer&gt;</code> directives gives me this output:</p> <pre><code>$VAR1 = { 'stuff2' =&gt; 'stuff', 'stuff' =&gt; 'stuff' }; </code></pre> <p>Of course, this has the side effect that $::object is updated by successful <code>object</code> productions even if the higher level rules fail (including backtracking). I'd write it this way:</p> <pre><code>use strict; use warnings; use Parse::RecDescent; use Data::Dumper; my $parser = Parse::RecDescent-&gt;new(&lt;&lt;'EOT'); event_function: object_list ':' event_list(?) ';' { $return = $item[1]; } object_list : &lt;leftop: object ',' object&gt; { $return = { map { %$_ } @{$item[1]} }; } object : '/' /[a-z0-9_][a-z0-9_]*/ '/' '...' { $return = { $item[2] =&gt; 'stuff' }; } | /[a-z0-9_][a-z0-9_]*/ { $return = { $item[1] =&gt; 'stuff' }; } # stub, don't know what this should be event_list : /[^;]+/ EOT my %object; while (&lt;DATA&gt;) { my $x = $parser-&gt;event_function($_); next unless $x; # merge objects into master list while (my ($k, $v) = each %$x) { $object{$k} = $v; } } print Dumper \%object; __DATA__ stuff, stuff2: pre-operation event = {foo1, foo2}; stuff3, stuff4: ; </code></pre> <p>The output is:</p> <pre><code>$VAR1 = { 'stuff2' =&gt; 'stuff', 'stuff3' =&gt; 'stuff', 'stuff' =&gt; 'stuff', 'stuff4' =&gt; 'stuff' }; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POParse::RecDescent - getting information from it
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMichael Carman
    1. USMichael Carman
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POParse::RecDescent - getting information from it
      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. VTAcceptedByOriginator
    1. COThat makes a kind of evil sense. Sigh. Thank you.
      singulars
      1. PO
      1. USPaul Nathan
 

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