sq VS Dapper

You can use my library sq which handles this exact use case with the PreparedQuery type. It allows you to build a query programmatically, prepare it and optionally rebind parameters by name.

Have you seen my library https://github.com/bokwoon95/sq? You can use it like database/sql and write plain SQL strings, only needing to provide a function that maps an database row to a struct and generics returns a slice of those structs at the end.

Also consider my library sq which handles dynamic query generation as well as data mapping. You may find it simpler than bun because it's a lot closer to database/sql (it doesn't require a special DB object, it uses a plain *sql.DB).

> I didn't see anything to help me build back graphs

Hmm you've certainly given me something to think about. Thanks.

BTW joins are not challenging, but you made me realize I didn't show any joins in my basic examples. Here is UPDATE with JOIN example: https://bokwoon.neocities.org/sq.html#postgres-update-with-j....

How does it compare to https://github.com/bokwoon95/sq?

Using Dapper to get database names from the SQL-Server instance set in appsettings.json

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.