- postgresql-simple VS postgresql-transactional
- postgresql-simple VS mbtiles
- postgresql-simple VS postgresql-schema
- postgresql-simple VS hocilib
- postgresql-simple VS haskey-btree
- postgresql-simple VS postgresql-simple-named
- postgresql-simple VS gremlin-haskell
- postgresql-simple VS postgresql-libpq
- postgresql-simple VS HongoDB
- postgresql-simple VS yxdb-utils
Postgresql-simple Alternatives
Similar projects and alternatives to postgresql-simple
-
-
Stream
Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.
-
-
-
-
-
-
postgresql-simple-named
:question: Implementation of named parameters for `postgresql-simple` library
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
-
-
-
-
-
-
postgresql-simple discussion
postgresql-simple reviews and mentions
-
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
Stats
lpsmith/postgresql-simple is an open source project licensed under BSD 3-clause "New" or "Revised" License which is an OSI approved license.
The primary programming language of postgresql-simple is Haskell.