Is it a mistake if that's all you need?
I'm kind of on the side of avoiding ORM unless you have a clear need for it. But I've seen projects where they are very valuable. If you mainly want to register, update and delete a bunch of structured data, it's not a bad idea to put it in a dabatase. And if you do those operations a lot in some part of the application, it's not a bad idea to use an ORM there. For analysis and reports and such I would probably suggest just writing SQL directly though.
It's hard to be sure that that's all you need. Maybe you'll be fine, maybe you'll get stuck between keeping a slow DB or rewriting everything. Doesn't cost much to go proper relational from the start. And if you're really sure you want objects, there are NoSQL solutions that are designed for that.
I think that’s part of why I’m having trouble with this framing - it’s treating CRUD as the entire universe of why you’d need to connect to a database.
Some of us do very intense compute in very large datasets, and ORM are not capable in those tasks. At all.
Doesn't even have to get very intense. A simple timeseries schema gets slow/annoying quickly with an ORM.
I think for a lot of things an ORM is “good” at, you could likely just have a bunch of static JSON files and retrieve them from disk with zero practical difference.
I just can’t wrap my head around why you even *need* a database in those cases.
You need a DB if you need to insert/update those objects transactionally, plus it's more convenient than mapping DB entries to files on disk. But you don't need an ORM for that anymore because Postgres and MySQL have json/jsonb types.
If you think of relational DBs as just CRUD machines, an ORM makes total sense, but that's the original mistake.