The naming convention of custom foreign keys and shadow attributes conflicts. Types that can be null cannot be null during migration

[zhuangState]

The naming convention of custom foreign keys and shadow attributes conflicts. Types that can be null cannot be null during migration
Nullable AccountID

Migration result cannot be empty

If you do not use the name AccountID, this problem will not be caused

[zhuangState]

It is normal without specifying a foreign key

[ErikEJ]

Which EF Core version and provider?

[zhuangState]

Hello, version 6.0.9

[ajcvickers]

This issue is lacking enough information for us to be able to fully understand what is happening. Please attach a small, runnable project or post a small, runnable code listing that reproduces what you are seeing so that we can investigate.

[ajcvickers]

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.

BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.