Breaking changes in Community Toolkit v9

[adrianhall]

Hey folks,

I thought I would start a thread to document all the breaking changes that I am introducing into Datasync Community Toolkit v9, all of which are due to breaking changes in the underlying libraries (Microsoft OData, System.Text.Json, EF Core, etc.)

Breaking Change 1: Client-side evaluation is no longer supported.

In the server, we turn a $filter coming in from the client into an IQueryable, which is then executed by the database. In v8, if this produced an exception because "client-side evaluation is required", we silently downloaded the entire data set and did the client-side evaluation for you. In v9, this same filter will now make the server produce a 400 Bad Request or 500 Invalid Server Error (depending on what exception is thrown by the database driver).

This affects Cosmos through EF Core mostly as the Cosmos query capabilities have a few important limitations:

• No math operations within a query.
• Cannot access a date part (like Year) of a DateTime or DateTimeOffset.
• Cannot query against a DateOnly or TimeOnly value.

Thanks to @richard-einfinity on alerting me of the Cosmos changes which uncovered this issue at the same time.