I think ORM...

I think what is Orm:
Answers Questions for beginners, Orm, object-Relation Mapping, and object link ing. It is mainly used to implement the correspondence between business logic and data tables in relational databases. Let you get rid of the details of accessing the database.

I think ORM is good:
I think the best thing about ORM is that you don't need to write SQL, connection, command, or dataadapter. Of course, it is convenient to change the database.

I think ORM is not good:
1,The most important thing is: put the cart before the horse if it is not good. With Orm, addCodeGeneration, I feel that as long as there is a database, the entire project will be almost done. It is easy to let people have a feeling of first making a database, then generating code, then modifying it, and adding a GUI. So, right? I don't need to talk about it?
2. database-driven development. Is it a word I made? Is anyone using a database-driven development?
3. Easy to use. xml and businessobject must be configured... code Generation is better, but I always feel uneasy about what is generated. Even if I write it myself (I also wrote it), there may be many problems (is my level not high enough ?). In addition, it is particularly difficult to switch from the carefully crafted code in the business logic to the wholesale code generation code.
4. Performance: Are all reflected? Expensive stuff...
5. The support for complex queries is poor: Multi-table joint queries and so on. Some of them can also be implemented, but it is more difficult to write SQL.

What do I think ORM is suitable:
1. Create a micro-system, especially with low concurrency or no concurrency.
2. Build a prototype system.

Thank you for your criticism. Your criticism is my best teaching material. :)