cypher
esqueleto
| cypher | esqueleto | |
|---|---|---|
| - | 5 | |
| 19 | 177 | |
| - | 0.0% | |
| 0.0 | 0.0 | |
| almost 12 years ago | over 7 years ago | |
| Haskell | Haskell | |
| BSD 3-clause "New" or "Revised" 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.
cypher
We haven't tracked posts mentioning cypher yet.
Tracking mentions began in Dec 2020.
esqueleto
-
Revisiting Haskell after 10 years
Writing Haskell programs that rely on third-party packages is still an issue when it’s a not actively maintained package. They get out of date with the base library (Haskell’s standard library), and you might see yourself in a situation where you need to downgrade to an older version. This is not exclusive to Haskell, but it happens more often than I’d like to assume. However, if you only rely on known well-maintained libraries/frameworks such as Aeson, Squeleto, Yesod, and Parsec, to name a few, it’s unlikely you will face troubles at all, you just need to be more mindful of what you add as a dependency. There’s stackage.org now, a repository that works with Stack, providing a set of packages that are proven to work well together and help us to have reproducible builds in a more manageable way—not the solution for all the cases but it’s good to have it as an option.
-
How to use PostgreSQL with Haskell: persistent + esqueleto
However, we can use Esqueleto (”a bare bones, type-safe EDSL for SQL queries”) with Persistent's serialization to write type-safe SQL queries. It’s unlikely that you want to use Persistent by itself with SQL, so let’s use and review them together.
-
What databases do you find the most productive to connect to Haskell?
Postgresql-simple is a great library, it makes a nice use of overloaded strings to do the job. Some other nice libraries to keep an eye on are opaleye (postgres specific, which is equally nice but could be a bit difficult to get why the types are so big) and a combination of persistent (not DB specific! can work on postgres, sqlite, but also noSQL DBs like mongo, it's still easy to learn but you lose some things, such as joins due to the power of being agnostic) + esqueleto for type safe joins (be sure to look up the experimental package, it's a more comfortable syntax that will soon become the default one).
-
Notes on Luca Palmieri's Zero to Production in Rust
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
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?
datalog - A pure Haskell implementation of Datalog
opaleye
eventful-dynamodb - Event Sourcing library for Haskell
yxdb-utils - Utilities for parsing Alteryx Database format
haskelldb - A library for building re-usable and composable SQL queries.
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
hsparql - hsparql includes a DSL to easily create queries, as well as methods to submit those queries to a SPARQL server, returning the results as simple Haskell data structures.
hocilib - A lightweight Haskell binding to the OCILIB C API
bloodhound - Haskell Elasticsearch client and query DSL
beam - A type-safe, non-TH Haskell SQL library and ORM
cassy - High level Cassandra bindings for Haskell
mysql-simple - A mid-level client library for the MySQL database, intended to be fast and easy to use.