Efcore: Query: Nested InvocationExpression may not work
Looking at https://github.com/aspnet/EntityFrameworkCore/issues/17791#issuecomment-571645107
and source code, we may not be expanding nested invocation expression. We should add a regression test for it. (And fix it in the process if not working, should be easy one liner).
smitpatel
All 7 comments
Hi, is it possible to see this fix on ef 3.1.0?
GiannisParaskevopoulos
on 12 May 2020
@GiannisParaskevopoulos See the release planning process for general information on how we determine which issues to patch for. Please post details on how this bug specifically is impacting your application.
ajcvickers
on 12 May 2020
@ajcvickers Hi and thanks for your response. I guess, I'll have to wait until November.... After all, i do have a workaround.
GiannisParaskevopoulos
on 13 May 2020
@GiannisParaskevopoulos may I ask what workaround you have for this issue?
merrycoder
on 28 Aug 2020
@ajcvickers this bug blocks us from migrating from 2.2 to 3.1 as we extensively use the PredicateBuilder in our search algo. We don't plan to migrate to 5.0 as it's not going to be a LTS version, so our next upgrade will be 6.0. I would immensely appreciate a fix in 3.1, if there is no workaround available for this issue.
merrycoder
on 28 Aug 2020
@GiannisParaskevopoulos any chance you could share the workaround with us?
MTrachsel
on 31 Aug 2020
Updated milestone to 3.1.9. The fix for this will be available in EF Core 3.1.9 or higher & EF Core 5.0 preview1 or higher release.
smitpatel
on 10 Sep 2020
Related issues
ericvb
路
3Comments
HeMinzhang
路
3Comments
leak
路
3Comments
yukozh
路
3Comments
pachecosoftware
路
3Comments
Most helpful comment
@ajcvickers this bug blocks us from migrating from 2.2 to 3.1 as we extensively use the PredicateBuilder in our search algo. We don't plan to migrate to 5.0 as it's not going to be a LTS version, so our next upgrade will be 6.0. I would immensely appreciate a fix in 3.1, if there is no workaround available for this issue.