Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You made a mistake when writing the <code>publisher</code> function:</p> <pre><code>foreverR $ do bs &lt;- await finallyF (ZMQ.close s M.&gt;&gt; ZMQ.term c M.&gt;&gt; print "ZMQ socket closed") $ do (liftU $ ZMQ.send s [] bs) (liftU (print "Sending message")) </code></pre> <p>You probably wanted to place the <code>finallyF</code> OUTSIDE the <code>foreverR</code> loop:</p> <pre><code>finallyF (...) $ foreverR $ do bs &lt;- await liftU $ ZMQ.send s [] bs) liftU (print "Sending message") </code></pre> <p>The way you wrote it, it finalizes after each send, so it's doing exactly what you told it to do: finalize after every send. <code>finallyF</code> calls the finalizer once the action it wraps is complete, both if it terminates successfully or unsuccessfully. You could also use <code>catchF</code> in that case, since the loop never terminates anyway:</p> <pre><code> catchF (...) $ foreverR $ do bs &lt;- await liftU $ ZMQ.send s [] bs) liftU (print "Sending message") </code></pre> <p>Alternatively, you could have kept it inside the loop but switched to <code>catchF</code> so that the finalizer doesn't get run after each send:</p> <pre><code>foreverR $ do bs &lt;- await catchF (ZMQ.close s M.&gt;&gt; ZMQ.term c M.&gt;&gt; print "ZMQ socket closed") $ do (liftU $ ZMQ.send s [] bs) (liftU (print "Sending message")) </code></pre> <p>Also, if you are planning on writing a zeroMQ library based on pipes, keep in touch with me because I'm planning to return frames back to an ordinary monad in the next release with a lot of new enhancements to functionality, too, such as the ability to close and reinitialize resources. To reach me use my gmail.com address with username Gabriel439.</p>
    singulars
    1. This table or related slice is empty.
    1. POFinalization in Pipes-2.1.0 package
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USGabriel Gonzalez
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POFinalization in Pipes-2.1.0 package
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you Gabriel both for the answer to this question and the nice pipes package.
      singulars
      1. PO
      1. USEric
    2. CO@Eric I forgot to mention that you probably want the first or second example as the latter one will not catch anything. `catchF` and `finallyF` only intercept pipe termination, but there is no chance of another pipe terminating when you only run actions in just the base monad.
      singulars
      1. PO
      1. USGabriel Gonzalez
 

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