Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This whole sub is really confusing, and I'm a fairly regular perl user. Here are some blanket suggestions.</p> <ul> <li>Do not create your own <code>undef</code> ever -- use <code>undef</code> then return at the bottom <code>return $var // 'NULL'</code>.</li> <li>Do not ever do this: <code>foreach $row</code>, because <code>foreach my $row</code> is less prone to create problems. Localizing variables is good.</li> <li>Do not needlessly concatenate, for it offends the style god: not this, <code>print "\nReturning: " . $thiskey . "\n";</code>, but <code>print "\nReturning: $thiskey\n";</code>, or if you don't need the first <code>\n</code>: <code>say "Returning: $thiskey;"</code> (5.10 only)</li> <li><code>grep</code>ing over <code>0 .. $#array;</code> is categorically lame, just grep over the array: <code>grep {} @{$foo[0]}</code>, and with that code being so complex you almost certainly don't want <code>grep</code> (though I don't understand what you're doing to be honest.). Check out <code>perldoc -q first</code> -- in short <em>grep doesn't stop until the end</em>.</li> </ul> <p>Lastly, do not assign an array to a scalar: <code>$thiskey = @result;</code> is an implicit <code>$thiskey = scalar @result;</code> (see <code>perldoc -q scalar</code>) for more info. What you probably want is to return the array reference. Something like this (which eliminates <code>$thiskey</code>)</p> <pre><code>printf "\nReturning: %s\n", join ', ', @result; @result ? \@result : 'NULL'; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POConverting code to perl sub, but not sure I'm doing it right
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USEvan Carroll
    1. USEvan Carroll
    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. 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. COGreat advice, ++. But, please be careful with potentially misleading vocabulary: "Localizing variables is good." In the context of "programming" this is excellent advice. In the context of "Perl programming" your statement is misleading, since it could be understood to mean that lexical and dynamic scopes are equivalent. The pesky fact that `local` and "localize" have a specific meaning in Perl that is distinct from the normal comp sci meaning of localize as "limit the scope of". How about changing the sentence to read "Minimizing the scope of variables is good." or something similar?
      singulars
      1. PO
      1. USdaotoad
    2. COI would rather use the [correct term](http://en.wikipedia.org/wiki/Local_variable) than a perl-specific work around to avoid connotation with the rather rarely used variable declaration `local`.
      singulars
      1. PO
      1. USEvan Carroll
 

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