Persistence interface for Haskell allowing multiple storage methods. (by yesodweb)

Pool-conduit Alternatives

Similar projects and alternatives to pool-conduit

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better pool-conduit alternative or higher similarity.

pool-conduit reviews and mentions

Posts with mentions or reviews of pool-conduit. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-05-06.
  • Was simplified subsumption worth it for industry Haskell programmers?
    6 projects | /r/haskell | 6 May 2022
    I don't think there's any malicious intent. It seems pretty clear that the motivation here is to simplify the type checker considerably, which is a really good reason to do something. Heck, I've got an open issue for deleting a feature in persistent which (according to the lack of comments on the issue) only ever used by persistent's own test suite.
  • [ANNOUNCE] GHC 9.2.2 is now available!
    4 projects | /r/haskell | 7 Mar 2022
    PR submitted: https://github.com/yesodweb/persistent/pull/1366 :)
  • Simple Servant + Persistent + Katip template for starting a new project
    5 projects | /r/haskell | 19 Jan 2022
  • Async Control Flow
    7 projects | /r/haskell | 21 Mar 2021
    Ha, I spotted a possible resource leak here. If stmtFinalize fail, then the connection won't be closed.
    7 projects | /r/haskell | 21 Mar 2021
    Hmm, you are right, the bracket I pointed to is unrelated. I guess the fix is in catchAny, which doesn't catch ThreadKilled. So not it's not rolling the transaction back in case of asynchronous exceptions. My point is that it probably should not rollback even on synchronous exception. BTW the issue is well know, see for example here
    7 projects | /r/haskell | 21 Mar 2021
    7 projects | /r/haskell | 21 Mar 2021
    I don't think connection is returned to the pool here. The thread is interrupted when query is sent to server, but before the results are consumed. At that point cleanup action catches `ThreadKilled` exceptions and issues `ROLLBACK`, which fails with `libpg` exception because the previous operations was not completed. And now cleanup action rethrows the `libpg` exception instead of the `ThreadKilled` one - that's the behavior of `bracket` from `base`. [The fix](https://github.com/yesodweb/persistent/pull/1207/files#diff-f9d7f232cd00cb88188b7fcc68110e3f4cb378fcad9df652360de44d13cd86e3R199) was to use `bracket` from `unliftio`, which [rethrows the correct exception](https://hackage.haskell.org/package/unliftio-0.2.14/docs/src/UnliftIO.Exception.html#bracket).
  • A note from our sponsor - #<SponsorshipServiceOld:0x00007f0f9aea9e20>
    www.saashub.com | 8 Dec 2023
    SaaSHub helps you find the best software and product alternatives Learn more →


Basic pool-conduit repo stats
8 days ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives