postgresql-simple vs esqueleto

postgresql-simple

Mid-level client library for accessing PostgreSQL from Haskell (by lpsmith)

#Database #Postgresql

Source Code

esqueleto

Bare bones, type-safe EDSL for SQL queries on persistent backends. (by prowdsponsor)

#Database

Source Code

hackage.haskell.org

Our great sponsors

SonarLint - Clean code begins in your IDE with SonarLint

Scout APM - Less time debugging, more time building

SaaSHub - Software Alternatives and Reviews

Our great sponsors

postgresql-simple		esqueleto
	Project
1	Mentions	2
210	Stars	177
-	Growth	0.0%
0.0	Activity	0.0
9 months ago	Latest Commit	over 5 years ago
Haskell	Language	Haskell
BSD 3-clause "New" or "Revised" License	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 | reddit.com/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

esqueleto

Posts with mentions or reviews of esqueleto. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-02-03.

Notes on Luca Palmieri's Zero to Production in Rust
1 project | reddit.com/r/rust | 26 Jun 2022

Using esqueleto in one of my haskell projects was a huge time sink and a major barrier to entry for colleagues.
Go performance from version 1.2 to 1.18
14 projects | news.ycombinator.com | 3 Feb 2022

In Haskell: https://hackage.haskell.org/package/esqueleto
Either it analyzes the given SQL to determine the in/out types of each SQL query, or it calls the database describe feature at compile-time.

What are some alternatives?

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

opaleye

haskey-btree - B+-tree implementation in Haskell

groundhog - This library maps datatypes to a relational model, in a way similar to what ORM libraries do in OOP. See the tutorial https://www.schoolofhaskell.com/user/lykahb/groundhog for introduction

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

yxdb-utils - Utilities for parsing Alteryx Database format

squeal-postgresql - Squeal, a deep embedding of SQL in Haskell

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

hasql - Performant PostgreSQL driver with a flexible mapping API

hocilib - A lightweight Haskell binding to the OCILIB C API

mbtiles - Haskell MBTiles Library

beam - A type-safe, non-TH Haskell SQL library and ORM

mysql-haskell - Pure haskell mysql driver

esqueleto vs opaleye

postgresql-simple vs haskey-btree

esqueleto vs groundhog