Alex Zaytsev
Alex Zaytsev
@heikar what is the full stack trace?
> Is the Optimize step necessary because EF also caches the query? This is needed because EF does not understand expressions if they are simply converted.
There is still a circular dependency via github.com/mwitkow/go-conntrack
Can you try manually expand the query and test if it works?
Likely a regression from #3306 / #3312
Changing `validOrders.Any(y => y == x.Order)` to `validOrders.Contains(x.Order)` solves your issue. I'll take a further look.
Th is not feasible because “C” is very expensive — currently 2418 characters long.
Anyway, that is how it was done initially. PS: characters aren’t missing. They are just not defined explicitly and using optimized encoder.
Was fixed in Hibernate here: https://github.com/hibernate/hibernate-orm/commit/4ebbf5b36da9fd9b6cee263d551e63c95c9ec349 I would prefer to have the similar implementation
Thanks. Good catch. @maca88, we would probably need to change the async generator to account for this situations.