hocilib
pool-conduit
Our great sponsors
- Onboard AI - Learn any GitHub repo in 59 seconds
- InfluxDB - Collect and Analyze Billions of Data Points in Real Time
- SaaSHub - Software Alternatives and Reviews
| hocilib | pool-conduit | |
|---|---|---|
| 0 | 9 | |
| 2 | 452 | |
| - | 1.1% | |
| 0.0 | 6.4 | |
| about 6 years ago | 2 days ago | |
| Haskell | Haskell | |
| BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
hocilib
We haven't tracked posts mentioning hocilib yet.
Tracking mentions began in Dec 2020.
pool-conduit
-
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).
What are some alternatives?
eventstore - EventStore Haskell TCP Client
persistent-odbc - uses persistent connecting via hdbc odbc
HongoDB - A Simple Key Value Store
selda - A type-safe, high-level SQL library for Haskell
beam - A type-safe, non-TH Haskell SQL library and ORM
HDBC - Haskell Database Connectivity
persistent-relational-record - Persistent adapter for Haskell Relational Record
ampersand - Build database applications faster than anyone else, and keep your data pollution free as a bonus.
hasql - The fastest PostgreSQL libpq-based driver for Haskell
postgresql-simple - Mid-level client library for accessing PostgreSQL from Haskell
dbmigrations - A library for the creation, management, and installation of schema updates for relational databases.
classy-influxdb-simple