Closed DominicArchual closed 2 years ago
Hi @DominicArchual, yes, as I see you use many strings in your ImportModel2. By default in QueryModelClass which is used internally there are just 3 string fields. You can bypass this limitation by creation custom QueryModelClass and put there as many string properties as you want (just use current version as template https://github.com/neisbut/EntityFramework.MemoryJoin/blob/master/src/EntityFramework.MemoryJoin/QueryModelClass.cs and add more string properties). Don't forget to use your QueryModelClass in DbSet in your context. Hope this helps.
@neisbut how do you register the extended query model class in the dbcontext, to allow memory join with the extended class ?
I'm experiencing an issue similar to this issue whereby passing a seemingly simple object into
FromLocalList
results in an error, "Too complex object."My project is configured for .NET 4.7.2 using EF 6:
Any idea what makes this array (which is not so far from the example) too complex for the method to handle? Is .NET 4.7.2 not supported?
I have also tried the following but the error returns, "Please include at least one property with
Long
type."The class definition of
ImportModel2
is as follows: