DapperQueryBuilder VS InterpolatedStrings

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