Sieve VS DapperQueryBuilder

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

When I first drafted this idea of concatenating FormattableStrings to build SQL, I didn't have any ambition to inherit from FormattableString, then in this new project (aimed at writing something more flexible/reusable and less coupled with Dapper) I realized that I was basically writing what you said - a mutable FormattableString. But yeah, when I rely on this new structure for SQL-Building I should pay extra attention to those risks.

How does this compare to Dapper Query Builder?

Yo! Love this library, makes it real easy to put together params for procs. Any headway on Issue #27? I've got a workaround but would love to be able to use multiple result sets natively.

My ideal vision is some higher level library that provides the DSL and parsing, and provides a way to either output Expressions for use with IQueryables or some other implementation to inject it into hand-written SQL queries. I have no clue if such a thing is even possible. I've found Sieve and DapperQueryBuilder. It seems like DapperQueryBuilder would support such a use case, using the Fluent API and conditionally adding Selects, Order By, Where, etc. Have you explored something similar? What did you find?

This project is just a fork of another QueryBuilder that I made for Dapper where manually building queries is much more important (as compared to EF where most queries will be made using LINQ expressions - I know).

LOL. Just a bored developer who saw an opportunity. :-) When I posted a few days ago about DapperQueryBuilder someone suggested that this same FormattableString-hacking could be used for Logging libraries. Since the major parts of processing FormattableString are identical (same regex, same loops, etc) and since I was a little bored this weekend I decided to try out this idea :-)