safe-exceptions
postgresql-simple
Our great sponsors
| safe-exceptions | postgresql-simple | |
|---|---|---|
| 3 | 1 | |
| 132 | 206 | |
| 0.0% | - | |
| 3.4 | 0.0 | |
| 6 months ago | over 2 years ago | |
| Haskell | Haskell | |
| MIT License | BSD 3-clause "New" or "Revised" 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.
safe-exceptions
-
Spooky Masks and Async Exceptions
In case anyone is interested, there's a long discussion on this ticket. Still hoping somebody will respond to my comment.
-
Async Control Flow
In safe-exception and uniftio it was decided to rethrow the original exception exactly because they decided to use uninterruptibleMask, see here for details.
-
Why exactly I want Boring Haskell to happen
unliftio (and safe-exceptions) contains a very controversial choice of of using uninterruptibleMask inside its bracket. The argument for it seem to come from this issue and comes from the fact that one of the most popular resource finalizers hClose is interruptible. This is a simplification. It is interruptible only if a file handle is used concurrently. Such usage of file handles is rather odd, and it suggest wrong architecture, for example leaking file handles using concurrency. When using file handles in synchronous setting, what withFile pattern encourages, hClose will not block and thus mask is enough.
postgresql-simple
-
Async Control Flow
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
What are some alternatives?
ifcxt - constraint level if statements
haskey-btree - B+-tree implementation in Haskell
unexceptionalio - IO without any PseudoExceptions
mbtiles - Haskell MBTiles Library
atl - Arrow Transformer Library
postgresql-schema - PostgreSQL Schema is a database migration tool.
effect-monad - Provides 'graded monads' and 'parameterised monads' to Haskell, enabling fine-grained reasoning about effects.
gremlin-haskell - Haskell graph database client for TinkerPop3 Gremlin Server
transient - A full stack, reactive architecture for general purpose programming. Algebraic and monadically composable primitives for concurrency, parallelism, event handling, transactions, multithreading, Web, and distributed computing with complete de-inversion of control (No callbacks, no blocking, pure state)
hocilib - A lightweight Haskell binding to the OCILIB C API
time-warp
postgresql-transactional - Transactional monadic actions on top of PostgreSQL.