I can only speak for pipes-postgresql-simple, but that is unsound almost by design (unfortunately). It turns out that the way it works means it is very easy to do things that break invariants. Iirc, opening a transaction inside a streamed query ends up terminating the streamed query early, but it still expects more rows.
On Mon, Jan 26, 2015 at 6:50 PM, Ben Moseley <b...@borde.rs> wrote: > I'm wondering what the current state-of-play is with pipes-concurrency. > > It looks interesting, but I'm made somewhat nervous about adopting it in > anger by: > > https://github.com/Gabriel439/Haskell-Pipes-Concurrency-Library/issues/27 > https://github.com/Gabriel439/Haskell-Pipes-Concurrency-Library/issues/28 > https://github.com/Gabriel439/Haskell-Pipes-Concurrency-Library/issues/29 > > https://www.haskell.org/pipermail/glasgow-haskell-users/2014-July/025107.html > > Also, presumably if pipes-concurrency is unsound, then so are mvc, > pipes-postgresql-simple, process-streaming etc as they all depend on it... > > Can anyone comment? > > --Ben > > -- > You received this message because you are subscribed to the Google Groups > "Haskell Pipes" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to haskell-pipes+unsubscr...@googlegroups.com. > To post to this group, send email to haskell-pipes@googlegroups.com. > -- You received this message because you are subscribed to the Google Groups "Haskell Pipes" group. To unsubscribe from this group and stop receiving emails from it, send an email to haskell-pipes+unsubscr...@googlegroups.com. To post to this group, send email to haskell-pipes@googlegroups.com.
