Thong Nguyen
Thong Nguyen
Hi @almostEric. What version of .NET is your server running? Is it .NET core? Shaolinq hasn’t been updated to support .NET core yet 😓
Hi @samcook, For context: The `IDataAccessModelHook` system was designed to be lightweight in terms of memory usage. This is why the `DataAccessModelHookSubmitContext.New`, `DataAccessModelHookSubmitContext.Updated`, `DataAccessModelHookSubmitContext.Deleted` properties are enumerables rather than lists...
@samcook Any comments?
Could you add a unit test?
TLDR but is this is an issue with SQL server only or all providers?
Yeah comparing with null is undefined so not(undefined) isn't true. I have to have a think about where else this affects could affect the framework because LINQ semantics for NULL...
Does this still fail? Could you provide an example?
Agreed. This is a open source project and we're always looking for volunteers to help...especially with documentation.
Can you try configuring the your logger (log4net or NLog etc) to log the logger named "Shaolinq. Query" at Debug level. Want to see what SQL your query is generating....
Before the log4net closing tag add: ``` ```