Generic Interceptor/Middleware for caching, retry, circuit breaker, etc. about sqlc HOT 2 OPEN

@StevenACoffman I came here looking for the same thing.

You can get these annotations by modifying the sqlc-gen-go template in internal/templates/./queryCode.tmpl.

That said, you didn't want to use the database/sql interface and I was unable to get prashanthpai/sqlcache to work using pgx/pgxpool directly. But that looks like a limitation of prashanthpai/sqlcache

I was able to get this to work by modifying the template in internal/templates/stdlib/queryCode.tmpl like so:

...
const {{.ConstantName}} = {{$.Q}}-- name: {{.MethodName}} {{.Cmd}}
{{range .Comments}}--{{.}}
{{end -}}
{{escape .SQL}}
{{$.Q}}
...

You can then write your query as:

-- name: ProductByZip :many
-- @cache-ttl 30
-- @cache-max-rows 100
select distinct p.name as product, v.name as vendor from product p
join vendors v on p.vendor = v.id
join vendorsa va on v.id = va.vendor
where va.zip = $1;

Hope this helps.

from sqlc.

@bldrdash Nice!

I filed an issue with jackc/pgx#1935 along the same lines, and the maintainer raised a good point.

The declarative nature of prashanthpai/sqlcache is nice, but the way sqlcache (and sqlmw) is implemented in the SQL driver, it requires a re-parse before deciding to just use the cached version. This makes the performance worse than it needs to be.

If the sqlc generated template Go code decided to attempt to use the cached version, it would not require re-parsing the SQL, so it would perform faster.

from sqlc.