Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You could raise an exception in the block and catch that exception.</p> <pre><code>module Tester class Breaker &lt; Exception; end class GoodBreak &lt; Breaker; end class BaadBreak &lt; Breaker; end end def test_block(name) begin yield rescue Tester::Breaker=&gt;e case e when Tester::GoodBreak then puts "All is well with #{name}" when Tester::BaadBreak then puts "BAD STUFF WITH #{name}" else raise end end end def good; raise Tester::GoodBreak; end def bad; raise Tester::BaadBreak; end test_block('early out') do good if true good if puts("NEVER SEE THIS") || true bad end test_block('simple pass') do good if false good if puts("SEE THIS FROM PASS TEST") || true bad end test_block('final fail') do good if false good if puts("SEE THIS BUT PUTS IS NIL") bad end #=&gt; All is well with early out #=&gt; SEE THIS FROM PASS TEST #=&gt; All is well with simple pass #=&gt; SEE THIS BUT PUTS IS NIL #=&gt; BAD STUFF WITH final fail </code></pre> <p>Here's another example using <code>throw/catch</code> (thanks @jleedev!) instead of <code>raise/rescue</code> (updated to pass a return value along):</p> <pre><code>def test_block(name) result = catch(:good){ catch(:bad){ yield } } puts "Testing #{name} yielded '#{result}'", "" end def good; throw :good, :good; end def bad; throw :bad, :bad; end test_block('early out') do good if true good if puts("NEVER SEE THIS") || true bad end test_block('simple pass') do good if false good if puts("SEE THIS FROM PASS TEST") || true bad end test_block('final fail') do good if false good if puts("SEE THIS BUT PUTS IS NIL") bad end #=&gt; Testing early out yielded 'good' #=&gt; #=&gt; SEE THIS FROM PASS TEST #=&gt; Testing simple pass yielded 'good' #=&gt; #=&gt; SEE THIS BUT PUTS IS NIL #=&gt; Testing final fail yielded 'bad' </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POReturn from block - from method called within block?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPhrogz
    1. USPhrogz
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POReturn from block - from method called within block?
      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. COThis might be a better application of `throw`/`catch`, since you’re using them for flow control. (Or call/cc. Heh.)
      singulars
      1. PO
      1. USJosh Lee
    2. CO@jleedev Right you are! It's been too long since I used those. Here is [introductory documentation on using throw/catch](http://phrogz.net/ProgrammingRuby/frameset.html?content=http%3A//phrogz.net/ProgrammingRuby/tut_exceptions.html%23catchandthrow) from the free first edition of Programming Ruby.
      singulars
      1. PO
      1. USPhrogz
    3. COThanks @Phrogz and @jleedev - I thought about using raise but kinda scared away from the thought after a lifetime of being told that exceptions are for "very bad situations"(tm) only ;) But the `throw`/`catch` way of doing it feels a lot less wrong!
      singulars
      1. PO
      1. USchris_sutter
 

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