postgresql-simple VS exceptions

Compare postgresql-simple vs exceptions and see what are their differences.

postgresql-simple

Mid-level client library for accessing PostgreSQL from Haskell (by lpsmith)
Database Postgresql
Source Code
Suggest alternative
Edit details

exceptions

mtl friendly exceptions (by ekmett)
Control
Source Code
Suggest alternative
Edit details
InfluxDB
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
Our great sponsors
postgresql-simple exceptions
1 1
206 48
- -
0.0 4.4
over 2 years ago 3 months ago
Haskell Haskell
BSD 3-clause "New" or "Revised" License BSD 3-clause "New" or "Revised" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

postgresql-simple

Posts with mentions or reviews of postgresql-simple. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-03-21.
  • Async Control Flow
    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

exceptions

Posts with mentions or reviews of exceptions. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-03-21.
  • Async Control Flow
    7 projects | /r/haskell | 21 Mar 2021
    I see. Do you think rethrowing the original exception is the the right approach in all cases, or only in this case? In the documentation I wrote for the exceptions package, I recommend to let the release block's exceptions take priority, to match base's behavior. Should I recommend the opposite?

What are some alternatives?

When comparing postgresql-simple and exceptions you can also consider the following projects:

haskey-btree - B+-tree implementation in Haskell

either - the EitherT monad transformer

mbtiles - Haskell MBTiles Library

control-monad-exception - Explicitly Typed exceptions as a library

hocilib - A lightweight Haskell binding to the OCILIB C API

failure - A simple type class for success/failure computations.

postgresql-schema - PostgreSQL Schema is a database migration tool.

categories - categories from category-extras

gremlin-haskell -  Haskell graph database client for TinkerPop3 Gremlin Server

control-monad-omega - A Haskell monad for fair enumeration of infinite sets.

postgresql-transactional - Transactional monadic actions on top of PostgreSQL.

hask - Category theory for Haskell with a lens flavor (you need GHC 7.8.3, not 7.8.2 to build this!)

postgresql-simple vs haskey-btree exceptions vs either postgresql-simple vs mbtiles exceptions vs control-monad-exception postgresql-simple vs hocilib exceptions vs failure postgresql-simple vs postgresql-schema exceptions vs categories postgresql-simple vs gremlin-haskell exceptions vs control-monad-omega postgresql-simple vs postgresql-transactional exceptions vs hask