Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This sounds like a case where you could make good use of <code>Future</code>s and <code>Executor</code>s. See more here:</p> <ul> <li><a href="http://java.sun.com/javase/6/docs/api/java/util/concurrent/Future.html" rel="nofollow noreferrer">http://java.sun.com/javase/6/docs/api/java/util/concurrent/Future.html</a></li> <li><a href="http://java.sun.com/javase/6/docs/api/java/util/concurrent/Executor.html" rel="nofollow noreferrer">http://java.sun.com/javase/6/docs/api/java/util/concurrent/Executor.html</a></li> </ul> <p>Here's a concrete example:</p> <pre><code>ExecutorService executor = Executors.newSingleThreadExecutor(); final Input input = ... Future&lt;Output&gt; future = executor.submit(new Callable&lt;Output&gt;() { public Output call() { return respond(input); } }); // do some work Output output = future.get(); // this blocks until it's done </code></pre> <p>In your case, since you mentioned that some of the fields in the <code>Output</code> object are to be used immediately, while others are used at a later point, you could structure your <code>Output</code> object to contain futures as fields. For example:</p> <pre><code>public class Output { private String fieldA; // immediate field private Future&lt;String&gt; fieldB; // delayed field public void setFieldA(String fieldA) { this.fieldA = fieldA; } public String getFieldA() { return fieldA; } public void setFieldB(Future&lt;String&gt; fieldB) { this.fieldB = fieldB; } public Future&lt;String&gt; getFieldB() { return fieldB; } } </code></pre> <p>You'd then structure your respond method like this:</p> <pre><code>public Output respond(final Input input) { Output output = new Output(); String fieldA = ... output.setFieldA(fieldA); Future&lt;String&gt; fieldBFuture = executor.submit(new Callable&lt;String&gt;() { public String call() { String fieldB = ... return fieldB; } } output.setFieldB(fieldBFuture); } </code></pre> <p>And to use your <code>Output</code> object:</p> <pre><code>Input input = ... Output output = respond(input); String fieldA = output.getFieldA(); // do some work String fieldB = output.getFieldB().get(); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POPre-creating objects in a separate thread
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmtpettyp
    1. UStoluju
    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@toluju I did not understand how `Executor`s can be useful in this context - can you please outline the algorithm?
      singulars
      1. PO
      1. USBinil Thomas
    2. CO@binil Added example for you, let me know if that clears things up.
      singulars
      1. PO
      1. UStoluju
    3. COtoluju, binil mentioned above that `Output` is provided by a 3rd-party library to which he has no source access; it looks like this method would require him to be able to modify the class, which he can't do.
      singulars
      1. PO
      1. USdelfuego
 

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