> And there is no worrying about the quality or correctness of generated code.
Although people are still very capable of writing terrible code.
The real, best reason to use an ORM is to piggyback on their migration management- the abject awful chaos of DIY migration tooling is difficult to describe.
That is an argument for using an ORM (or similar) to define the schema. I agree it is probably the biggest single advantage.
There are advantages for using an ORM for queries. Its more concise (at least Django ORM, which is what I mostly use), it uses the same syntax as the rest of your code, and it returns an object. It works very well for simple queries but for more complex ones it does sometimes feel like I am fighting the ORM, and you do often have to look at the generated SQL too.
Although people are still very capable of writing terrible code.
The real, best reason to use an ORM is to piggyback on their migration management- the abject awful chaos of DIY migration tooling is difficult to describe.