I'm actually surprised that EF is even able to trigger this, I assumed that the underlying SQL would trump a null insert. EF Core version: 3.1.4 Database provider: (e.g.