stomasovic

@sdanyliv , it is hard to move to version 6, even slight upgrade to version 3.6 or 3.7. breaks some of our expression logic. Sometimes in future, we will eventually...

I understand that it is hard to maintain older version. My main intention was to understand if I can change query in some way that it works or to get...

We added retry mechanism, and when randomly fails, next retry call to that Queryable completes successfully, without any error. Does it has some caching or whatever so we can fix...

@sdanyliv , nope, we did not override ProcessQuery to change SQL AST. Do you think we should? Even if we do, not sure how to validate if Aliases are fine....

I resolved issue on other part of the system, by adding Sql.AsSql. Here is the part of the expression used in some IQueryable that causes it, and how I resolved...

@sdanyliv , I upgraded from 3.5.2. to 3.7.0. and it is having same issue, so that upgrade will not help. Next, I upgraded to 5.4.1. and that version, seems fixed...

Seems that Future queries have issues as well. Tests were running fine, but some failed with: ``` Message:  Oops! A general error has occurred. Please report the issue including the...

Unfortunately, no isolated tests. It is hard to reproduce, except load our JobScheduling component to generate those emails. As mentioned above, in UnitTests, we load it heavily with a lot...