Open douglasg14b opened 1 month ago
Alright, I managed to make the problem go away by:
Is this intentional behavior, or a bug?
It's definitely a bug - we should never throw exception like that possibly related to https://github.com/dotnet/efcore/issues/33452
Well that's awkward, I remember writing in repro code into this, but upon revisiting this issue I see now such thing in the description. 😬
I must have never clicked save, cripes.
File a bug
I've read a few issues on this and have been unable to gleam much information from them
Include your code
I'm still trying to figure out what might be triggering this, I do not have a trivial repro at this time. The affecting code is a lot of business logic that, in the end, adds a new related entity, and deleted & adds an owned entity.
Include stack traces
Include the full exception message and stack trace for any exception you encounter.
Use triple-tick fences for stack traces. For example:
Attempts:
record
to class`: No Change ❌record
and update it withAdlogicLink with { State = newState }
to get a whole new instance. ✅Include verbose output
No problems here.
Include provider and version information
EF Core version: 8.0.4 Database provider: Postgres Target framework: .NET 8 Operating system: Windows 10 IDE: Rider 2024.1.2