DapperQueryBuilder VS Dapper

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 :-)

In both samples to get all records and to get a single record works fine but there is a better way to perform the same work using NuGet package Dapper. Dapper is extremely easy to use and built with performance in mind. In the source code provided the basic operations are covered, to take things to the next level and read the information at GitHub, the following page and other code samples in the following repository.

In this article learn how to use Dapper an open-source object-relational mapping (ORM) library for .NET and .NET Core applications. Unlike many articles out there, this one will provide source code to try everything out that is shown in an easy-to-follow way by beginning with a single table then in part two of this series will work with multiple tables.

Dapper

I will be using Dapper - a simple object mapper for .Net along with MySqlConnector.

Maybe the more basic approach to dapper is their documentation https://github.com/DapperLib/Dapper the readme but again most likely you not gonna understand

I think EF Core & EF are the successors to LINQ to SQL that you'd wanna look into, and/or Dapper if you wanna go lower.

The main maintainers of Dapper no longer work at Stack, but they're active enough to comment on recent pull requests: https://github.com/DapperLib/Dapper/pull/1887.

MarieDB and dapper https://github.com/DapperLib/Dapper