-
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
Merge relational and regular table docs #1717
Conversation
947b957
to
4bccb9a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. Some comments.
@roji What's the state here? There is a lot of conversation above between you and Diego; do these still need to be resolved? |
Yep, I'm planning to pick this up again now that we're done with 3.1. It would be good to get another opinion on the state of the PR as-is before I do. |
d67c08a
to
ba46584
Compare
@ajcvickers (and @aspnet/efteam in general) I rebased this and did some minor tweaks, but otherwise left as-is. Take a look at Diego's comments and tell me what you think. Once we establish how we want it to be I'll go and do the same to the rest of the modeling docs. |
Pushed some changes. |
23497ad
to
8744336
Compare
* Merged modeling/relational/tables and modeling/relational/default-schema into modeling/included-types and renamed to types-and-tables. * Show DataAnnotation/FluentAPI as tabs Part of #1669
Part of #1669
Notes/questions:
The configuration in this section is applicable to relational databases in general. The extension methods shown here will become available when you install a relational database provider (due to the shared Microsoft.EntityFrameworkCore.Relational package)
). As we're merging relational and non-relational docs, it seems OK to remove this note, and to textually call out when documenting a relational-only feature.