-
Notifications
You must be signed in to change notification settings - Fork 2k
Document breaking changes for complex types in EF Core 10.0 #5113
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
Document breaking changes for complex types in EF Core 10.0 #5113
Conversation
…els with value converters Co-authored-by: AndriySvyryd <[email protected]>
entity-framework/core/performance/advanced-performance-topics.md
Outdated
Show resolved
Hide resolved
entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
Outdated
Show resolved
Hide resolved
entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
Outdated
Show resolved
Hide resolved
samples/core/Miscellaneous/CompiledModels/ValueConverterSample.cs
Outdated
Show resolved
Hide resolved
…sections Co-authored-by: AndriySvyryd <[email protected]>
entity-framework/core/performance/advanced-performance-topics.md
Outdated
Show resolved
Hide resolved
entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
Outdated
Show resolved
Hide resolved
entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
Outdated
Show resolved
Hide resolved
entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
Outdated
Show resolved
Hide resolved
entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
Outdated
Show resolved
Hide resolved
entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
Outdated
Show resolved
Hide resolved
entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
Outdated
Show resolved
Hide resolved
…, reorganize sections Co-authored-by: AndriySvyryd <[email protected]>
entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
Outdated
Show resolved
Hide resolved
Co-authored-by: AndriySvyryd <[email protected]>
@copilot Update the description with a short summary and reference the fixed issues dotnet/efcore#35033 and #4970 |
Updated the PR description with a short summary of the breaking changes documented and added references to the fixed issues #35033 and #4970. |
{ | ||
public static readonly BooleanToCharConverter Default = new(); | ||
|
||
public BooleanToCharConverter() |
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.
nit: maybe modernize the code sample a bit, with a primary constructor, expression-bodied methods below?
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.
@copilot modernize the code sample a bit, with a primary constructor and expression-bodied methods
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.
Modernized the code sample to use a primary constructor and expression-bodied methods for the conversion methods. (1d1a23e)
|:--------------------------------------------------------------------------------------------------------------- | -----------| | ||
| [SQL Server json data type used by default on Azure SQL and compatibility level 170](#sqlserver-json-data-type) | Low | | ||
| [ExecuteUpdateAsync now accepts a regular, non-expression lambda](#ExecuteUpdateAsync-lambda) | Low | | ||
| [Compiled models now throw exception for value converters with private methods](#compiled-model-private-methods) | Low | |
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.
@copilot please align indentation here so that the markdown table is formatted correctly/consistently.
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.
Fixed the markdown table indentation alignment. (94791e4)
entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
Outdated
Show resolved
Hide resolved
|
||
#### Old behavior | ||
|
||
Previously, when mapping complex types to table columns, if multiple properties in different complex types had the same column name, they would silently share the same column. |
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.
How does this relate to the breaking change just below - are they dups? In other words, if the full path is now used (the change below), how is it possible to for multiple properties in different complex types to have the same column name (i.e. when would appending the number be necessary)?
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.
It's less likely, but still possible if the user explicitly set the column name on one that matches the default column name of the other.
Co-authored-by: roji <[email protected]>
@AndriySvyryd am slightly confused by certain things here (see comments) but I'm sure it's my misunderstanding etc. |
…methods Co-authored-by: AndriySvyryd <[email protected]>
Co-authored-by: AndriySvyryd <[email protected]>
This PR documents breaking changes for EF Core 10.0 related to complex types.
Breaking Changes Documented
Complex Types (#4970)
ProcessDiscriminatorPropertySet
method now takesIConventionTypeBaseBuilder
instead ofIConventionEntityTypeBuilder
Changes Made
Fixes #4970
Fixes #4947
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.