dotnet / dotnet/EntityFramework.Docs

Document trade-offs in string store-type mappings

Open
#1,103 3 comments 0 reactions 0 assignees View on GitHub
area-entity-mapping
Dominant language
Mermaid
Stars
1.7k
Forks
2k
Avg merge
7d 23h
Merged PRs (30d)
16

Description

For example, is it a good idea, in terms of performance concerns, to use the default convention and let all string properties be mapped to nvarchar(max) columns, or it's better to set a fixed length (e.g. 500) globally to all string properties?

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 8d6f6f7b-b8d3-df80-33b7-46b0b98acd29
* Version Independent ID: 1a74a6d8-0ad4-9a22-d62e-1a2bab8b80b1
* Content: [Maximum Length - EF Core](https://docs.microsoft.com/en-us/ef/core/modeling/max-length)
* Content Source: [entity-framework/core/modeling/max-length.md](https://github.com/aspnet/EntityFramework.Docs/blob/master/entity-framework/core/modeling/max-length.md)
* Product: **entity-framework**
* GitHub Login: @rowanmiller
* Microsoft Alias: **divega**

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.