Arthur Vickers
Arthur Vickers
@AminEsmaeily You can configure the max length as unspecified again like this: ```C# modelBuilder.Entity() .Property("Discriminator") .HasMaxLength(-1); ``` Note for team: the index exception is unfortunate here. We don't create indexes...
@mycroes Use whatever you prefer or has the characteristics you need.
Note for triage: this is a consequence of https://github.com/dotnet/efcore/pull/29771, which stopped using common prefixes to generate navigation names. @shikamu [Custom T4 templates](https://learn.microsoft.com/en-us/ef/core/managing-schemas/scaffolding/templates?tabs=dotnet-core-cli) can be used to customize the navigation names...
Note from triage: the new behavior is preferable to the old behavior, but for cases where the old behavior was reasonable we should document this as a breaking change.
@shikamu There is no specific template for this. Start from the default templates and edit the code that writes the navigation names.
Note for triage: in this case the query is explicitly creating instances of the principal entity, which means that we don't do identity resolution here for tracking queries either.
@SudoWatson EF Core uses case-insensitive key comparisons by default for SQL Server. (This is new in 8.0.) You can switch case-sensitive comparisons using the steps here: https://learn.microsoft.com/en-us/ef/core/modeling/value-conversions?tabs=data-annotations#use-case-insensitive-string-keys. (These steps show...
@MJWRijkers Have you created an configured your own case-sensitive comparer? By default, EF uses a case-insensitive comparer for SQL Server key properties, starting with EF8. You'll need something like this:...
The default was case sensitive until EF8, when it changed to case insensitive.