Provide a way to control client evaluation behavior on a per query basis

[divega]

Based on the feedback we usually see this is very common and something like an AsServerOnly() query operator would be more usabel than the current way to turning client evaluation warnings into errors.

[optiks]

An extension method on IQueryable for this would be great.

My main use case is where .ConfigureWarnings(warnings => warnings.Throw(RelationalEventId.QueryClientEvaluationWarning)) has been configured on the context, but where I still want to allow some client evaluation to occur (most likely because there is no server-side support).

i.e. I don't want an error thrown if there's nothing I can do to fix it.

[smitpatel]

@optiks - Calling AsEnumerable method on IQueryable will allow you to do client evaluation even when warnings are configured to throw.

[ajcvickers]

Added to Qu3ry issue.

[optiks]

@smitpatel, AsEnumerable() isn't discoverable enough nor explicit enough IMO. I don't see how AsEnumerable() implies that client-evaluation is acceptable?

[smitpatel]

AsEnumerable is similar to calling ToList. You are asking EF to materialize query results upto that point, whatever happens afterwards is outside of EF scope (aka client eval). If client eval in EF is throwing exception then it would also tell you what failed to translate which gives easy pointer where to put AsEnumerable in your query.

[optiks]

Please also consider whether it would make sense to provide a predicate on Throws, i.e. something like warnings.Throw(RelationalEventId.QueryClientEvaluationWarning, query => /* some logic* / true). I'm not sure what the appropriate type for query would be.

I think this would let us then implement this behaviour ourselves if necessary, especially if the Expression was provided.

[ajcvickers]

Closing as not needed now since the query changes for 3.0.