SaaSHub helps you find the best software and product alternatives Learn more →
Pool-conduit Alternatives
Similar projects and alternatives to pool-conduit
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
persistent-relational-record
Persistent adapter for Haskell Relational Record
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
ghc-proposals
Proposed compiler and language changes for GHC and GHC/Haskell
-
-
servant-persistent-template
Simple servant-persistent template with up to date libraries, multipart form data API, basic User management model, property testing, simple JWT authentication, example public/private routes, among other features
-
-
-
bytestring
An efficient compact, immutable byte string type (both strict and lazy) suitable for binary or 8-bit character data.
-
cryptonite
Discontinued lowlevel set of cryptographic primitives for haskell
-
postgresql-simple
Mid-level client library for accessing PostgreSQL from Haskell
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
pool-conduit reviews and mentions
-
Was simplified subsumption worth it for industry Haskell programmers?
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!
PR submitted: https://github.com/yesodweb/persistent/pull/1366 :)
- Simple Servant + Persistent + Katip template for starting a new project
-
Async Control Flow
Ha, I spotted a possible resource leak here. If stmtFinalize fail, then the connection won't be closed.
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
https://github.com/yesodweb/persistent/blob/f69716dcfeca01896ec42dec874393fbe60d3939/persistent/Database/Persist/Sql/Run.hs#L212
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 - SaaSHub
www.saashub.com | 28 Mar 2024
Stats
yesodweb/persistent is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of pool-conduit is Haskell.