Personal opinion about sqlc.
- Solid code generation
- Write SQL statements as-is, no need for a complex ORM query builder
- It actually checks if the queries are valid when generating code, which allows for catching errors early in the dev process
- The generated code is straightforward to use
- Works well with existing migration tooling such as go-migrate
- Documentation is ok, but not that extensive
- Can configure/override parts of the generated code
- Can be used to work with PostGIS to some extent
- Sometimes the documentation is a bit lacking
- Does not support PostGIS data types out of the box
- Not possible to create custom types that maps to certain Golang structs
- For example:
geometryin PostGIS can be of many types such as a point, line, polygon, etc. We cannot distinguish between these different subtypes at this point of time
- For example:
$ docker compose up$ exec dev ./run-test.sh
- Define the type of your field in the query when possible, this will help sqlc infer the correct type for the field. Sometimes it falls back to
interface{}when not doing so. - When working with PostGIS data types you can render them as a string and process that separately