[CW]
Content warning
Golang and SQL, why do I even bother
Show
Hide
Content warning
Golang and SQL, why do I even bother
Started writing a way to handle data from an API to and from a local database, in go with SQL, just using the SQLite driver, only to stop because I don't want to have to manage the types that I get from the API.
Turns out it's an awful lot easier to just use sqlc to generate code from the schema/queries and write a converter between the API model and the sqlc one. I'm not sure why I even tried.
Turns out it's an awful lot easier to just use sqlc to generate code from the schema/queries and write a converter between the API model and the sqlc one. I'm not sure why I even tried.