Tune Hyperdrive caching or rotate its credentials
d1 & hyperdrive
// what it does
Grab the config id from list (or get), then update in place without recreating the binding. Tune --max-age (how long cached query results live) and --swr (stale-while-revalidate window) for read-heavy workloads, or pass a new --connection-string to rotate the origin password. Use --caching-disabled when you need strong consistency.
// shell
$ wrangler hyperdrive list$ wrangler hyperdrive update <id> --max-age=60 --swr=15$ wrangler hyperdrive update <id> --connection-string="postgres://user:newpassword@host:5432/dbname"// gotcha
update, get and delete take the config id, not the name you created it with — list maps names to ids. Caching only ever applies to non-mutating, identical read queries; writes are never cached.