opaleye

By tomjaguarpaw

Opaleye Alternatives

Similar projects and alternatives to opaleye

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better opaleye alternative or higher similarity.

opaleye reviews and mentions

Posts with mentions or reviews of opaleye. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-02-28.
  • What's your favorite Database EDSL/library in Haskell?
    4 projects | /r/haskell | 28 Feb 2023
    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
    2 projects | /r/haskell | 9 Feb 2023
    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)
    1 project | /r/haskell | 28 May 2022
    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?
    4 projects | /r/haskell | 21 Apr 2022
  • Out of memory when building product-profunctors
    2 projects | /r/haskell | 13 Mar 2022
    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
    1 project | /r/haskell | 5 Sep 2021
  • How to simply do opaleye field type conversion
    1 project | /r/haskell | 21 Jul 2021
  • Against SQL
    8 projects | news.ycombinator.com | 10 Jul 2021
    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.

    [1] https://github.com/tomjaguarpaw/haskell-opaleye/

  • Combining Deep and Shallow Embedding of Domain-Specific Languages
    1 project | /r/haskell | 31 Jan 2021
    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).
  • A note from our sponsor - SaaSHub
    www.saashub.com | 25 Apr 2024
    SaaSHub helps you find the best software and product alternatives Learn more →

Stats

Basic opaleye repo stats
9
593
8.5
12 days ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com