Products · Product
Ecto
Raised as a usability problem by 11 people on Hacker News over 9 years (2017–2025), in 12 threads.
No issue was raised by at least 3 people in 3 threads this year.
No issue was raised by at least 3 people in 3 threads in the last 5 years.
Every issue, all time, most people first
Hard to figure out how to express complex SQL queriesUnreviewed
20172026- Advanced Ecto docs are confusing; mixing inline and piped queries requires an extra variable2023-11-10
- Ecto's join query syntax is needlessly abstract and hard to read2021-09-15
- Hard to figure out how to express complex SQL queries in Ecto2021-05-18
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 12 complaints
- Couldn't figure out how to use Ecto; official docs weren't helpful2025-04-13
- Advanced Ecto docs are confusing; mixing inline and piped queries requires an extra variable2023-11-10
- Every migration change requires manually restoring structure.sql or migration won't run2023-02-25
- Undocumented macro-based query syntax is hard to guess and understand2022-08-20
- Having to include all fields and clumsier changesets feel harder than ActiveRecord2021-12-20
- Ecto's join query syntax is needlessly abstract and hard to read2021-09-15
- Hard to figure out how to express complex SQL queries in Ecto2021-05-18
- Queries are too verbose and awkward to write for one-off console tasks2021-03-19
- Inconsistent calling syntax forces constant reference to examples to get code right2020-10-01
- Debugging Ecto and changesets is hard; returned data is confusing to inspect2019-10-17
- Ecto is unnecessarily complex and slows developers down2019-08-10
- Ecto is too low level, forcing teams to write lots of wrapper code2017-10-27