codesnips
go 29 lines · 1 tab

db/sql prepared statements with context and explicit Close

Leah Thompson Jan 2026
1 tab 
package store

import (
  "context"
  "database/sql"
)

type Queries struct {
  db         *sql.DB
  getByEmail *sql.Stmt
}

func New(db *sql.DB) (*Queries, error) {
  stmt, err := db.Prepare(`SELECT id FROM users WHERE email = $1`)
  if err != nil {
    return nil, err
  }
  return &Queries{db: db, getByEmail: stmt}, nil
}

func (q *Queries) Close() error {
  return q.getByEmail.Close()
}

func (q *Queries) UserIDByEmail(ctx context.Context, email string) (string, error) {
  var id string
  err := q.getByEmail.QueryRowContext(ctx, email).Scan(&id)
  return id, err
}
1 file · go Explain with highlit

Prepared statements are useful when the same query runs in hot loops, but they come with lifecycle responsibilities. I prepare once (usually at startup), store the *sql.Stmt, and always close it on shutdown. The important detail is still using QueryRowContext so deadlines and cancellations work; prepared statements don’t magically inherit context. This pattern is also safer than building SQL strings in loops and it can reduce parse overhead on the database side. In production, I pair this with context.WithTimeout at the handler layer and with metrics for query latency so slow queries are obvious. The example below shows a small wrapper that provides a typed method around a prepared statement, keeping call sites clean and consistent.

Related snips

go 
package api

import (
  "net/http"
  "runtime/debug"
)

Expose build metadata for debugging deploys

go observability build
by Leah Thompson 1 tab
go 
package dbutil

import (
  "context"

  "github.com/jackc/pgconn"

Retry Postgres serialization failures with bounded attempts

go postgres transactions
by Leah Thompson 1 tab
ruby 
require "csv"

class PeopleCsvStream
  include Enumerable

  HEADERS = %w[id full_name email signed_up_at plan].freeze

Resilient CSV Export as a Streamed Response

rails performance streaming
by codesnips 3 tabs
ruby 
Rails.application.configure do
  config.after_initialize do
    Bullet.enable = true
    Bullet.alert = false
    Bullet.bullet_logger = true
    Bullet.console = true

N+1 query detection with Bullet gem

rails performance activerecord
by Alex Kumar 2 tabs
ruby 
# BAD: N+1 query problem
@users = User.all
@users.each do |user|
  puts user.posts.count  # Fires query for each user!
end

ActiveRecord query optimization and N+1 prevention

ruby rails activerecord
by Sarah Mitchell 3 tabs
ruby 
json.array! @posts do |post|
  json.cache! ['v1', post], expires_in: 1.hour do
    json.id post.id
    json.title post.title
    json.excerpt post.excerpt
    json.published_at post.published_at

Fragment caching for expensive JSON serialization

rails caching performance
by Alex Kumar 1 tab

Share this code

Here's the card — post it anywhere.

db/sql prepared statements with context and explicit Close — share card
Link copied