Null Reference due to missing sqlAliasManager due to double nullable optimisation #35507
Labels
Comments
|
Confirmed, thanks for submitting @ocdi - see below for a minimal repro (it's always appreciated if the repro can be narrowed down as much as possible, like the below). await using var context = new TestContext();
await context.Database.EnsureDeletedAsync();
await context.Database.EnsureCreatedAsync();
_ = context
.Set<Item>()
.Select(a => a.OwnerId!)
.Where(a => context
.Set<Item>()
.Select(a => a.OwnerId)
.Take(100)
.Contains(a))
.ToListAsync();
public class Item
{
public int Id { get; set; }
public string? OwnerId { get; set; }
}
public class TestContext : DbContext
{
public DbSet<Item> Items { get; set; }
protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
=> optionsBuilder
.UseSqlServer("Server=localhost;Database=test;User=SA;Password=Abcd5678;Connect Timeout=60;ConnectRetryCount=0;Encrypt=false")
.LogTo(Console.WriteLine, LogLevel.Information)
.EnableSensitiveDataLogging();
} |
|
Probably the same as #35192. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
I have a query that after upgrading to EFCore 9 stopped working. The query in the main system is performing paginated syncing in chunks.
The bug appears to be in how the optimiser is handling nullability, with an IN clause having both sides nullable.
Your code
This code demonstrates the bug. The master branch is .NET9, downgrading to EFCore 8 + .NET8 the code runs (
net8branch).https://github.com/ocdi/ef9bug
Note the code includes a bunch of extra complexity that mirrors more of what we are syncing, turns out the bug is triggered with much less in the first projection. The complexity is in how we're doing the pagination perhaps. It was difficult to trigger this code path, if I make
OwnerId/OwnerTyperequired on the Item class, the bug does not happen.Stack traces
This is from debugging with symbols loaded
This is the console output from the test project linked.
Verbose output
EF Core version
9.0.1
Database provider
SqlServer
Target framework
.NET 9.0
Operating system
No response
IDE
No response
The text was updated successfully, but these errors were encountered: