Databases
StackOverflow2013
Postsdbo
PONested Iteratees
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONested Iteratees
    primarykey
    data
    text
    <p>I am working with a particular database where, upon a successful query, you are able to access a group of chunks of the resulting data using a specific command:</p> <pre><code>getResultData :: IO (ResponseCode, ByteString) </code></pre> <p>Now getResultData will return a response code and some data where the response codes look like this:</p> <pre><code>response = GET_DATA_FAILED | OPERATION_SUCCEEDED | NO_MORE_DATA </code></pre> <p>The ByteString is one, some, or all of the chunks:</p> <p><a href="http://desmond.imageshack.us/Himg189/scaled.php?server=189&amp;filename=chunksjpeg.png&amp;res=medium" rel="nofollow noreferrer">Data http://desmond.imageshack.us/Himg189/scaled.php?server=189&amp;filename=chunksjpeg.png&amp;res=medium</a></p> <p>The story does not end here. There exists a stream of groups:</p> <p><a href="http://desmond.imageshack.us/Himg695/scaled.php?server=695&amp;filename=chunkgroupsjpeg.png&amp;res=medium" rel="nofollow noreferrer">Stream http://desmond.imageshack.us/Himg695/scaled.php?server=695&amp;filename=chunkgroupsjpeg.png&amp;res=medium</a></p> <p>Once receiving a NO_MORE_DATA response from getResultData, a call to getNextItem will iterate the stream allowing me to start calls to getResultData again. Once getNextItem returns STREAM_FINISHED, that's all she wrote; I have my data.</p> <p>Now, I wish to remodel this phenomenon with either Date.Iteratee or Data.Enumerator. Inasmuch as my existing Data.Iteratee solution works, it yet seems very naive and I feel as if I should be modeling this with nested iteratees as opposed to one big iteratee blob which is how my solution is currently implemented.</p> <p>I have been looking at the code of Data.Iteratee 0.8.6.2 and I am a bit confused when it comes to the nested stuff.</p> <p><strong>Are nested iteratees the proper course of action? If so, how would one model this with nested iteratees?</strong></p> <p>Regards</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USExternalReality
    1. USExternalReality
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PONested Iteratees
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PONested Iteratees
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PONested Iteratees
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI've never actually used Data.Iteratee or Data.Enumerator, but I feel the following questions are relevant nonetheless: Are chunks a fixed size? And, do you ever get partial chunks with `getResultData`, or do they always come through as whole chunks? The same questions apply to "groups".
      singulars
      1. PONested Iteratees
      1. USDan Burton
    2. COGroups are of fixed size, but the command that reads the chunks from the groups may not always get the whole of the group in one call. The outer box is a group the inner boxes are chunks which, again, may or may not be read in a single call to getResultData.
      singulars
      1. PONested Iteratees
      1. USExternalReality
 

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