-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encourage a level of familiarity with the chosen RDBMS before using EF Core #2657
Comments
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. |
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 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. |
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.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: