4 ms·

Curious what you think makes it better than other examples out there? How is it different than Active Record or Prisma?

• cultofmetatron 3y ago
  the list would merit its own dedicated blog post but to highlight a few nice parts, ecto lets me write sql code in elixir. it does not try to wrap it all into objects but I do get schemas. so for instance I can create a schema `Player` which maps to a table "players" I can then get them via ``` from(p in Player) |> where([p], p.id in ^player_ids) |> select([p], p) |> Repo.all() ``` need to join with an association? ``` from(p in Player) |> join([p], s in assoc(p, :scores), as: :score) |> where([p], p.id in ^player_ids) |> preload([p, score: s], [score: s]) |> select([p], p) |> Repo.all() ``` this gets me all players with their scores. need to get the sum of scores for all players? ``` from(p in Player) |> join([p], s in assoc(p, :scores), as: :score) |> where([p], p.id in ^player_ids) |> select([p], %{ player_id: p.id, score: sum(score.value) }) |> group_by([p, score: s], [p.id]) |> Repo.all() ``` as you can see, you can unwind this pretty fast to sql in your head. but you can also let the system just grab the kitchen sink when you jsut need to get somethign working fast. and its all very easy to modify and decuple. this is hardly exhaustive though, I could spend a day talking about ecto. I spent 8 years developing in nodejs but now I work exclusively in elixir. unless what you're doing is 90% done by existing libraries, its juts a better tool for building highly performant backends.
  • spion 3y ago
    Have you tried drizzle? https://orm.drizzle.team/docs/select#aggregations https://orm.drizzle.team/docs/select#aggregations (note: it produces type-safe results too)
    • KRAKRISMOTT 3y ago
      Their migrations tool is proprietary and not open-source. The project is basically an open source bait and switch riding off the edge computing hype (since prisma and other major JS ORMs have poor support for edge environments).
      • spion 3y ago
        You don't need to use drizzle migrations. There are much better migration tools.
  • invaliduser 3y ago
    This is probably great to use, but it also highlights in comparison the beautiful simplicity of SQL. Doing something simple is hard, and SQL is so simple that I think most people find little value to abstractions built on it.
    • kiliancs 3y ago
      There are different valid ways to produce these queries, some of which might be less composable but simpler: https://hexdocs.pm/ecto/Ecto.Query.html https://hexdocs.pm/ecto/Ecto.Query.html
• esafak 3y ago
  prisma appears to have a transaction problem. https://github.com/prisma/prisma/discussions/12715 https://github.com/prisma/prisma/discussions/12715
  • misnome 3y ago
    Wow, a project describing itself as a “Next generation ORM” that… doesn’t do joins, with no way to optimise queries. Perhaps they mean “Next generation” as in, the 1987 TV series sense. Which would still be a long time after the concept of joins…
    • djbusby 3y ago
      To boldly go where the problem was solved ages ago
    • pstuart 3y ago
      There's One Weird Trick™ in managing joins in this case -- create views that implement the joins and then just treat it as yet another table. Bonus feature is creating a consistent way of working with that relation using native DB tools. ;-)
      • cultofmetatron 3y ago
        that works great till your database gets big. Then you will watch your memory use skyrocket to perform joins into that view and it will F@#$@# your shit up. eventually it will take so much time to construct your view table that you'll tiemout your connection pool. to be clear, dont' use views in production queries. you WILL regret it. source: made this mistake.
  • meekaaku 3y ago
    Really wow. Such a basic feature should be available in beta version