Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>They'll only be equivalent if the first thing after breaking out of the loop is a <code>return</code> statement.</p> <p>In any case, if your lecturer doesn't allow <code>break</code>, they probably won't allow <code>return</code> either.</p> <p>You should be aware that these rules have a good basis behind them (to prevent spaghetti code and make it easier to write maintainable code) but sometimes they're enforced over-zealously.</p> <p>For example, there's <em>nothing</em> unreadable about the segment:</p> <pre><code>if (x == 0) return 0; return x - 1; </code></pre> <p>even though it has multiple <code>return</code> statements.</p> <p>The supposedly preferred solution to the no-multiple-return crowd is something like:</p> <pre><code>int y = x - 1; if (x == 0) y = 0; return y; </code></pre> <p>which is, in my opinion, both less readable and a waste of space.</p> <p>The real problems occur when you have very complex logic and the hoops that people jump through to avoid <code>break</code> and/or <code>return</code> leads to conditionals that are darn-near unreadable.</p> <p>Listen to your lecturer - they are, after all, the ones in control of what grade you get. Then, once you get into the real world, you can switch from dogmatism to pragmatism and make up your own mind.</p> <p>See <a href="https://stackoverflow.com/questions/216359/break-statements-in-the-real-world/216375#216375">here</a> for some good advice regarding these issues outside of educational institutions.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs it bad style to use 'return' to break a for loop in Java?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USpaxdiablo
    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. CO+1 Nice explanation, although I think that enforcing such rules in school (while starting to learn) might help. I.e., when people can't use some tool sensibly yet, it's better to not use it at all. (I was talking about a `break`: I see no way how you can 'overuse' `return`)
      singulars
      1. PO
      1. USNikita Rybak
    2. CONot being able to use a tool sensibly yet is a result of a lack of experience. The code you hand-in in school isn't going to be useful for anything except your own learning, so you may as well get the most bang for your buck and use and abuse as many features as you can and hence discover first hand what's a bad idea. Up with guidance, down with dogmatism!
      singulars
      1. PO
      1. USE.M.
    3. COthe problem can be solved at the language level too. For example people liked to be "pragmatic" about the indent (4 or 8 spaces, whatever) and about where to put braces (on a new line or not)... Then designers like the ones behind Google's "Go" language came up with mandatory indent and brace location **in the language specs**. No more arguing, no more *"dogmatism vs pragmatism"*. It's defined in the spec. A language could conceivably mandate one and only one return statement and poof, so much for *dogmatism vs pragmatism"* :)
      singulars
      1. PO
      1. USGugussee
 

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