> While you’re still researching the best SQL library for a project
People do this? In every language I've worked with, there's practically just one SQL library to use. And you just write a query, execute it, and map some results. Very basic.
Come on, that’s not what you really do, but an oversimplification that skimps on the actually hard parts.
You manage (as few as possible) connections to a DBMS, create prepared statements, cache and transform results, lazily iterate over large result sets, batch writes, manage schema migrations, and more. It’s not very basic, unless you’re cobbling up a prototype.
> In every language I've worked with, there's practically just one SQL library to use.
Curious which languages that were. In practically all ecosystems I know, there are 2-4 contenders.
People do this? In every language I've worked with, there's practically just one SQL library to use. And you just write a query, execute it, and map some results. Very basic.