ActiveRecord

Raised as a usability problem by 10 people on Hacker News over 15 years (2010–2024), in 11 threads.

People raised many different problems with ActiveRecord, but no single problem has yet been raised by 3 people in 3 different months and threads.

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 10 complaints

Implicit loading and saving of associations surprises developers about when database calls happen2024-11-10
Must hop around object hierarchy to tell what query is generated2024-10-24
Built-in query building is too complicated beyond the getting started tutorial2023-06-28
Inefficient GROUP BY queries slowed a page, and debugging took a long time2021-04-21
Writing or optimizing complex queries requires hunting down obscure Rails-specific incantations2019-09-09
Must manually keep model boilerplate in sync with database schema changes, which is tedious2018-06-08
Models serve as both repositories and single-row objects, making the API messy2018-05-21
Anything beyond simple CRUD is near-impossible without falling back to raw SQL2014-05-02
Query API is arcane and takes a long time to learn2012-07-13
Too annoying to use outside a gem environment due to funkiness2010-02-21