Document temporal period properties mapped to CLR properties#5336
Merged
roji merged 2 commits intodotnet:preview.4from Apr 16, 2026
Merged
Document temporal period properties mapped to CLR properties#5336roji merged 2 commits intodotnet:preview.4from
roji merged 2 commits intodotnet:preview.4from
Conversation
There was a problem hiding this comment.
Pull request overview
Documents the EF Core 11 capability to map SQL Server temporal period columns (PeriodStart/PeriodEnd) to CLR properties (instead of shadow properties), improving direct access in queries and entities.
Changes:
- Added a “Temporal period properties mapped to CLR properties” section to EF Core 11 “What’s New” (with mapping + query examples).
- Updated SQL Server temporal tables docs to clarify shadow properties are the default and added a new section showing CLR mapping configuration and usage.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| entity-framework/core/what-is-new/ef-core-11.0/whatsnew.md | Adds an EF Core 11 “What’s New” subsection describing CLR-mapped period properties with examples and a link to detailed docs. |
| entity-framework/core/providers/sql-server/temporal-tables.md | Updates narrative to mention CLR mapping support and adds a dedicated section describing configuration options and query usage. |
AndriySvyryd
approved these changes
Apr 16, 2026
Member
AndriySvyryd
left a comment
There was a problem hiding this comment.
Did you mean to target main instead of preview.4?
Member
Author
|
Good catch. |
Document the new EF Core 11 feature that allows temporal period properties (PeriodStart/PeriodEnd) to be mapped to CLR properties instead of being restricted to shadow properties. Updates: - temporal-tables.md: New 'Mapping period columns to CLR properties' section with lambda and string-based configuration examples - temporal-tables.md: Updated existing text to note shadow properties are the default, with links to the new section - whatsnew.md (EF Core 11): New subsection under SQL Server Relates to dotnet/efcore#38110 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
4190711 to
3861454
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the new EF Core 11 feature from dotnet/efcore#38110 that allows temporal period properties (
PeriodStart/PeriodEnd) to be mapped to CLR properties on the entity type, instead of being restricted to shadow properties.Changes
entity-framework/core/providers/sql-server/temporal-tables.mdHasPeriodStart/HasPeriodEndconfiguration exampleValueGenerated.OnAddOrUpdatebehavior noteentity-framework/core/what-is-new/ef-core-11.0/whatsnew.md