Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As Peter Lawrey commented, this is almost certainly going to be simpler as nested loops. More over, the <a href="http://code.google.com/p/guava-libraries/wiki/FunctionalExplained">Guava documentation</a> gives this warning:</p> <blockquote> <p>Imperative code should be your default, your first choice as of Java 7. You should not use functional idioms unless you are absolutely sure of one of the following:</p> <ul> <li>Use of functional idioms will result in net savings of lines of code for your entire project. Moving the definition of a function to another file, or a constant, does not help. </li> <li>For efficiency, you need a lazily computed view of the transformed collection and cannot settle for an explicitly computed collection. Additionally, you have read and reread Effective Java, item 55, and besides following those instructions, you have actually done benchmarking to prove that this version is faster, and can cite numbers to prove it. </li> </ul> <p>Please be sure, when using Guava's functional utilities, that the traditional imperative way of doing things isn't more readable. Try writing it out. Was that so bad? Was that more readable than the preposterously awkward functional approach you were about to try?</p> </blockquote> <p>However, if you're insistent on ignoring advice, you could use something like this monstrosity (note I haven't actually tried to compile or run this):</p> <pre><code>FluentIterable.from(continentList) .transform(new Function&lt;Continent, Void&gt;() { public Void apply(Continent continent) { return FluentIterable.from(continent.getCountries()) .transform(new Function&lt;Country, Void&gt;() { public Void apply(Country country) { return FluentIterable.from(country.getCities()) .transform(new Function&lt;City, Void&gt;() { public Void apply(City city) { // do stuff with city object return null; } }); } }); } }); </code></pre> <p>Now ask yourself: Which would you want to maintain? Which is going to be the most efficient?</p> <p>There are valid use-cases for Guava's functional idiom. Replacing Java for loops, even nested for loops, is not one of them.</p>
    singulars
    1. This table or related slice is empty.
    1. POGuava iterators, and iterating over a list within a list object
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USLouis Wasserman
    1. USig0774
    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. COUsing [`FluentIterable.transformAndConcat()`](http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/collect/FluentIterable.html), you can chain the transformations instead of nesting them, though.
      singulars
      1. PO
      1. USFrank Pavageau
    2. CO@FrankPavageau: True. But even if that's going to be a bit cleaner, it's still going to be uglier and less readable than the nested loops.
      singulars
      1. PO
      1. USig0774
    3. CO@ig0774 Thanks for the pro-tip :)
      singulars
      1. PO
      1. USGobiasKoffi
 

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