sqlc-gen-go-server

Sqlc plugin to generate gRPC, Connect or HTTP server from SQL.

Usage

version: '2'
plugins:
- name: go-server
  wasm:
    url: https://github.com/walterwanderley/sqlc-gen-go-server/releases/download/v0.1.0/sqlc-gen-go-server.wasm
    sha256: "bdd6fd13a062f9319c4ab13cbdc359c0275b531b8698be51ff843904bf919a5c"
sql:
- schema: schema.sql
  queries: query.sql
  engine: postgresql
  codegen:
  - plugin: go-server
    out: internal/db
    options:
      package: db
      sql_package: pgx/v5
      server_type: grpc

All plugins options.

Customizing HTTP endpoints

You can customize the HTTP endpoints (server_type: http or grpc) by adding comments to the queries.

-- http: Method Path

Here’s an example of a queries file that has custom HTTP endpoints:

-- name: ListAuthors :many
-- http: GET /authors
SELECT * FROM authors
ORDER BY name;

-- name: UpdateAuthorBio :exec
-- http: PATCH /authors/{id}/bio
UPDATE authors
SET bio = $1
WHERE id = $2;

Post-process for server_type: http

Note: If you’d rather not execute these steps, you might want to use sqlc-http instead of this plugin.

After execute sqlc generate you need to organize imports and fix go.mod.

1. Install the required tools:

go install golang.org/x/tools/cmd/goimports@latest

2. Organize imports:

goimports -w *.go **/*.go **/**/*.go

3. Fix go.mod:

go mod tidy

4. If you define more than one package, you’ll need to add them to the generated registry.go file.

Post-process for server_type: grpc or connect

Note: If you’d rather not execute these steps, you might want to use sqlc-grpc or sqlc-connect instead of this plugin.

After execute sqlc generate you need to organize imports, compile protocol buffer and fix go.mod.

1. Install the required tools:

go install golang.org/x/tools/cmd/goimports@latest
go install github.com/grpc-ecosystem/grpc-gateway/v2/protoc-gen-grpc-gateway@latest
go install github.com/grpc-ecosystem/grpc-gateway/v2/protoc-gen-openapiv2@latest
go install google.golang.org/protobuf/cmd/protoc-gen-go@latest
go install google.golang.org/grpc/cmd/protoc-gen-go-grpc@latest
go install connectrpc.com/connect/cmd/protoc-gen-connect-go@latest
go install github.com/bufbuild/buf/cmd/buf@latest

2. Organize imports:

goimports -w *.go **/*.go **/**/*.go

3. Compile the generated protocol buffer:

buf mod update proto
buf generate

4. Fix go.mod:

go mod tidy

5. If you define more than one package, you’ll need to add them to the generated registry.go file.

Plugin options

You can use all of the Golang plugin's options as well as the options described below.

version: 2
plugins:
- name: go-server
  wasm:
    url: https://github.com/walterwanderley/sqlc-gen-go-server/releases/download/v0.1.0/sqlc-gen-go-server.wasm
    sha256: "bdd6fd13a062f9319c4ab13cbdc359c0275b531b8698be51ff843904bf919a5c"
sql:
- schema: "query.sql"
  queries: "query.sql"
  engine: "postgresql"
  codegen:
  - plugin: go-server
    out: "internal/db"
    options:
      server_type: "http" # The server type: grpc, connect or http.      
      module: "my-module" # The module name for the generated go.mod.
      metric: false # If true, enable open telemetry metrics.
      tracing: false # If true, enable open telemetry distributed tracing.
      litefs: false # If true, enable support for distributed SQLite powered by embedded LiteFS.
      litestream: false # If true, enable support for continuous backup sqlite to S3 powered by embeded Litestream.
      migration_path: "" # If you want to execute database migrations on startup.
      migration_lib: "goose" # The database migration library. (goose or migrate)
      skip_go_mod: false # If true, skip the generation of the go.mod.
      skip_queries: "" # Comma separated list (regex) of queries to ignore
      append: false # If true, enable the append mode and do not generate the editable files.

Building from source

Assuming you have the Go toolchain set up, from the project root you can simply make all.

make all

This will produce a standalone binary and a WASM blob in the bin directory. They don't depend on each other, they're just two different plugin styles. You can use either with sqlc, but we recommend WASM and all of the configuration examples here assume you're using a WASM plugin.

To use a local WASM build with sqlc, just update your configuration with a file:// URL pointing at the WASM blob in your bin directory:

plugins:
- name: go-server
  wasm:
    url: file:///path/to/bin/sqlc-gen-go-server.wasm
    sha256: ""

As-of sqlc v1.24.0 the sha256 is optional, but without it sqlc won't cache your module internally which will impact performance.