System.Linq.Dynamic.Core VS Sieve

We have an app that was written with core 3.1 and uses Postgres and Marten to create a document store. I have several tables with filtering functionality that uses DymanicLinq (https://dynamic-linq.net/) to generate queries. As 3.1 is EOL, we are upgrading to NET 6 but doing so seems to have broken the queries. I now get exceptions saying the Specified Method is unsupported. Anyone have any idea how to fix this?

How is it different from Dynamic Linq?

Fun with expression trees, pretty cool!. How does this compare with Dynamic Linq?

Have a look at Dynamic LINQ I am using it in a similar fashion to yourself to accept 'order' and 'where' parameters via API Endpoints and parsing them to LINQ queries

-> Dynamic LINQ

Not much to explain, other than: https://dynamic-linq.net/

RulesEngine runs on any arbitrary object since it's based on Dynamic LINQ. It can be used outside of SQL for evaluating expressions. This allows business rules to be changed w/out compilation, publishing or devops.

Biarity/Sieve: ⚗️ Clean & extensible Sorting, Filtering, and Pagination for ASP.NET Core (github.com)

I´m trying out Sieve and the rip my app to pieces and use that instead.

Similar to Sieve

https://github.com/Biarity/Sieve Sieve is a simple, clean, and extensible framework for .NET Core that adds sorting, filtering, and pagination functionality out of the box. Most common use case would be for serving ASP.NET Core GET queries.

If you're looking for a library for a REST API, there really aren't very many good ones. I used Sieve as a starting point to write my own because it didn't support the filtering syntax I was required to use. I would definitely not recommend a new person write their own, however.

I also looked at Sieve: https://github.com/Biarity/Sieve but I'm not sure it is 100% hitting what I am wanting. Unless I am just a bork at the end of my day unable to read properly. Any direction in the right area would greatly be appreciated!

For complex queries like this, you don't have a ton of choices. You could use Sieve (https://github.com/Biarity/Sieve) in lieu of your current implementation. I use it specifically in situations to handle filtering/paging/sorting, not as a general way to access data. Most of the time I write an underlying DB view and hook that up to a keyless entity and allow Sieve to do the actual filtering.

If you're using EF, you can use https://github.com/Biarity/Sieve