Products · Product
Prisma
Raised as a usability problem by 9 people on Hacker News over 7 years (2019–2025), in 8 threads.
No issue was raised by at least 3 people in 3 threads this year.
Every issue, all time, most people first
No built-in way to roll back a broken migrationUnreviewed
20192026- No built-in way to roll back a broken migration2024-02-10
- Migrate gets into a state users can't recover from, and the re-baselining docs don't work2023-10-14
- Migrations often fail, and understanding why requires knowing SQL2023-03-15
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 9 complaints
- Query objects become hard to read as queries grow more complex2025-05-15
- No built-in way to roll back a broken migration2024-02-10
- Migrate gets into a state users can't recover from, and the re-baselining docs don't work2023-10-14
- Hard to write non-trivial queries; constantly fighting the DSL and forced into raw SQL2023-10-10
- Using PostGIS types with Prisma is a terrible experience2023-06-21
- Migrations often fail, and understanding why requires knowing SQL2023-03-15
- Query-level caching is locked behind enterprise sales contact, with no trial2021-04-22
- Docs panels squeeze text into narrow columns, making them unreadable on phones2019-04-08
- Docs were unusable, with broken links and no mobile or iPad viewing2019-04-07