Maurycy Markowski
Maurycy Markowski
@paule96 apologies for delayed response. I'm able to reproduce this. Currently the way to specify default value is with fluent api: ``` protected override void OnModelCreating(ModelBuilder modelBuilder) { modelBuilder.Entity(b =>...
closing as duplicate of https://github.com/dotnet/efcore/issues/19546
@paule96 which scenario are you referring to? Those should have no impact on migrations whatsoever, e.g. for the second step, adding the following: ```cs public bool AfterInitBool { get; set;...
The problem is we were incorrectly computing the nullability of json reference - using `navigation.ForeignKey.IsRequired` rather than `navigation.ForeignKey.IsRequiredDependent`
@dashiell-zhang this issue has been fixed in the upcoming EF10 - we didn't fix it in time for EF9.
@boukenka at the moment we don't plan to port this to EF9, reason being that it's not a regression (scenario also fails on EF8) and relatively few people have hit...
reopening for potential patch
I can reproduce this on main. Problem is that when we try to see if we are comparing entity with optional dependent, we assume the entity will always be mapped...
@roji @AndriySvyryd @cincuranet @SamMonoRT can one of you guys take a quick look and sign off?
The suggestion that worked there was to use 'HandleNullPropagation = false' - EF is generally good at handling null protection itself (there were some issues in the past and I...