go-database-sql-tutorial VS go-essentials

I don't understand why modern project managers bite into object-oriented reading from relational databases like a dog to a bone. After all, SQL was created for processing relational databases, and attempts to bypass this language only lead to wasted resources and eerily slow queries. I had to fix a lot of such "pearls" made with Entity Framework (.NET/C#). Analogue GO language tools are no better. Use the GO language package dabase/sql, which is not only fast and easy, but also has an excellent tutorial (http://go-database-sql.org/).

I study database/sql using https://go-database-sql.org guide. At the time, I’m interested in prepared statements.

My advice I think would be to try and break this down into stages. First of all I think you need to get comfortable with how to work with a database from Go, so separately from your main application just create a new throwaway folder and start messing about with connecting and then inserting/retrieving data. This site has some good basic info about that part of things: http://go-database-sql.org/

I highly recommend to work yourself through this tutorial on how to properly use database/sql package.

Go database/sql tutorial is the de-facto resource for understanding how to work with this package together with examples using MySQL and PostgreSQL.