The way this documentation is presented makes using an ORM seem much simpler than it is in reality. It can lead to unexpected behaviour and performance problems that become apparent at a later stage in the application's life-cycle, once realistic data loads start to be encountered.
To avoid and troubleshoot these issues requires a substantial level of knowledge of the chosen RDBMS.
Such concepts include: Primary keys, foreign keys, constraints, indexes, normalization, DML statements, DDL statements, data types, using a profiler, admin tools, and probably more.
Perhaps consider adding an aside about this, with links to learning materials for the for the popularly supported RDBMSs.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Thanks for the suggestion.
@Rick-Anderson Can you please not close issues in this repo. We have a regular triage twice per week for new issues.
@lukesdm While I don't necessarily agree with your characterization of the issue, we do believe that having some more documentation in this area would be useful. This is tracked by #2106.
@lukesdm While I don't necessarily agree with your characterization of the issue, we do believe that having some more documentation in this area would be useful. This is tracked by #2106.
It would be useful to hear what you disagree with, if it's not too much trouble. Regardless, thank you very much for your response.
@lukesdm sorry I accidently closed this issue. As the team responds, review #2668. I don't see much different from what you asserted.
@lukesdm I believe it is reasonable for a developer to use EF Core even with little experience using relational databases. As the developer learns they may/should find places where they can improve what they are doing, but that doesn't mean they should feel afraid to even give things a try.