Maurycy Markowski

sending for retriage since our plans for json + value types

Can you provide a standalone repro that shows the problem? What is the exception that you are getting? In principle, Union on queryable sources is supported, but all depends on...

related: https://github.com/dotnet/efcore/issues/33517

Switching to lax would be too breaking, especially when collaborating with earlier versions. But making the setting configurable on sql server seems like a decent option.

FYI @roji This might go away if/when we get rid of nav expansion, also low priority bug, only happens in legacy mode and test case seems uncommon

@FM1973 try the following configuration instead: ```cs internal sealed class PollConfiguration : IEntityTypeConfiguration { public void Configure(EntityTypeBuilder builder) { builder.ToTable("Polls"); builder.HasKey(c => c.Id); builder.Property(c => c.Title).HasMaxLength(255).IsRequired(); builder.Property(c => c.Description).HasMaxLength(1000).IsRequired(false); builder.Property(c...

Problem here is that if inner OwnsMany contains a ToJson call, the navigation gets mapped to a Tasks JSON column in the database model, instead of the top level JSON...

We still should fix this, so that other people don't get hit by this. Will re-open, but it's not a high priority, given the easy workaround

I can't reproduce the problem on my end. I'm using the following code: ```cs using var ctx = new MyContext(); await ctx.Database.EnsureDeletedAsync(); await ctx.Database.EnsureCreatedAsync(); await ctx.Set().AddAsync(new Entity { Value =...

I'm able to reproduce this on current bits. Problem is that SqlExpressionFactory.Case applies TypeMapping for elseResult based on type mappings before we run type inference code - we use provided...