Nick Strupat
This is because new entities don't have "original values". The concept of original values is for entities that have already been persisted.
If the entity is new, the `Insert...` triggers will be raised. If it existed already, the `Update...` triggers will be raised.
I'm not sure that exception is coming from this library. I just did a global search for `provider` and didn't get any results for a parameter named `provider`. Do you...
I can't really help you with just a stack trace. I need to see code that recreates this issue.
It's a work-in-progress, on which progress has slowed lately. Are you blocked by a migration to EF Core?
I just wrote an extension method along these lines ```csharp static class SqliteExtensions { public static String ToQueryPlan(this IQueryable queryable) { using var command = queryable.CreateDbCommand(); command.CommandText = "explain query...
It's my understanding that any `T`s that are value types will be copied into their respective fields in the `OneOf` instance. Boxing them will allocate sizeof(T) + 16 bytes on...
No problem. Thank you for your responses and help so far :)
It depends on the relationship defined on those foreign keys. The entity you access through the Deleted event parameters is the same as if you had the entity reference itself...
I think you're right about the cascade delete behaviour. I think you can use the delete failed event to track whether the delete failed.