Note that there are some explanatory texts on larger screens.

plurals
  1. USuser770901
    primarykey
    data
    text
    plurals
    1. COWell, thanks, I guess. Hopefully someone can help me with the query structure for CouchDB and how best to get the desired information.
      singulars
    2. COI'm not sure what you mean by "with the minimal resources difference between every two tasks?". What the algorithm generates is the minimal number of resources needed to ensure no contention. Which is to say that every instruction can execute immediately when it is ready (when all it's predecessors have been executed). If the graph were visualized in "stages" corresponding to clock cycles, and there were only one resource type, this would correspond to the maximal width of the graph at a given stage. I'm doing it for multiple resource types.
      singulars
    3. COOkay, well, I've already done the first two things. It's the third I'm having trouble with. What do you mean "multiple values for one column"? Do you mean if the systemIDs already exist? Wouldn't it be more efficient to just get the "last" systemID already in the CouchDB and then add anything that's greater? Either way, that's not super helpful answer.
      singulars
 

Querying!

 
Guidance

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