|almost 10 years ago||16 days ago|
|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.
We haven't tracked posts mentioning bits-conduit yet.
Tracking mentions began in Dec 2020.
Was simplified subsumption worth it for industry Haskell programmers?
6 projects | reddit.com/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 | reddit.com/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 | reddit.com/r/haskell | 19 Jan 2022
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
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).
Using a different version of a package than what exists in resolver.
1 project | reddit.com/r/haskellquestions | 20 Mar 2021
text Cloning b1e32adfe1da49cd9df997a13bd0c5b391486f5c from https://github.com/yesodweb/persistent.git No cabal file found for Repo from https://github.com/yesodweb/persistent.git, commit b1e32adfe1da49cd9df997a13bd0c5b391486f5c
What are some alternatives?
HongoDB - A Simple Key Value Store
bloodhound - Haskell Elasticsearch client and query DSL
lmdb - Lightning MDB bindings for Haskell
hocilib - A lightweight Haskell binding to the OCILIB C API
mongoDB - MongoDB driver for Haskell
persistent-relational-record - Persistent adapter for Haskell Relational Record
HDBC - Haskell Database Connectivity
persistent-protobuf - a Template-Haskell routine to ease integration between Persistent and protobufs
persistent-template-classy - Generate classy lens field accessors for persistent models
persistent-generic - Generic facilities for working with Persistent classes
persistent-odbc - uses persistent connecting via hdbc odbc