opaleye
classy-influxdb-simple
Our great sponsors
| opaleye | classy-influxdb-simple | |
|---|---|---|
| 9 | - | |
| 594 | 1 | |
| - | - | |
| 8.5 | 0.0 | |
| 6 days ago | about 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.
opaleye
-
What's your favorite Database EDSL/library in Haskell?
If you ever have any questions about Opaleye I'm happy to help. Feel free to open an issue to ask about anything any time.
-
Persistent vs. beam for production database
Sounds like Opaleye isn't on your list of choices, but if it is then feel free to ask me any questions, any time by filing an issue (I'm the Opaleye maintainer).
-
How to build a large-scale haskell backend for a photo sharing app (some questions)
Opaleye is Posgres-only, and Postgres does such a good job of optimizing queries that performance issues basically don't arise. I have a long-standing invitation to improve Opaleye's query generation as soon as anyone can produce a repeatable example of a poorly-performing query. In Opaleye's eight years, no one ever has. There's a thread where two reports have come close, but it's still not clear that that's simply due to using a six year old version of Postgres.
- What are things that the Haskell scene lacks the most?
-
Out of memory when building product-profunctors
Nice! Well done. If you have any more questions about product-profunctors or Opaleye then please let me know. It's best to ask by [opening an issue](https://github.com/tomjaguarpaw/haskell-opaleye/issues/new).
- Embedded Pattern Matching
- How to simply do opaleye field type conversion
-
Against SQL
The only way out that I can see is to design embedded domain specific languages (EDSLs) that inherit the expressiveness, composability and type safety from the host language. That's what Opaleye and Rel8 (Postgres EDSLs for Haskell do. Haskell is particularly good for this. The query language can be just a monad and therefore users can carry all of their knowledge of monadic programming to writing database queries.
This approach doesn't resolve all of the author's complaints but it does solve many.
Disclaimer: I'm the author of Opaleye. Rel8 is built on Opaleye. Other relational query EDSLs are available.
-
Combining Deep and Shallow Embedding of Domain-Specific Languages
For an example of how this plays out in practice observe Opaleye's MaybeFields (generously contributed by Shane and /u/ocharles at Circuithub). The definition is essentially identical to Optional from the paper. Instead of a specialised typeclass Inhabited we use the ProductProfunctor NullSpec (which happens to conjure up an SQL NULL, but it could be any other witness).
classy-influxdb-simple
We haven't tracked posts mentioning classy-influxdb-simple yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
esqueleto - Bare bones, type-safe EDSL for SQL queries on persistent backends.
erd - Translates a plain text description of a relational database schema to a graphical entity-relationship diagram.
mywatch
acid-state - Add ACID guarantees to any serializable Haskell data structure
HDBC - Haskell Database Connectivity
pool-conduit - Persistence interface for Haskell allowing multiple storage methods.
database-migrate - database-migrate haskell library to assist with migration for *-simple sql backends.
dbmigrations - A library for the creation, management, and installation of schema updates for relational databases.
HongoDB - A Simple Key Value Store
sqlite-simple - Mid-level bindings for sqlite
squeal-postgresql - Squeal, a deep embedding of SQL in Haskell
HDBC-odbc - ODBC driver for HDBC