1 reply

Hyperdrive with postgres and Planetscale

Workers

Hi Cloudflare Support,

I am experiencing an issue where my Hyperdrive binding does not seem to provide the connectionString in the production environment unless I manually add a specific Secret.

My Setup:
- Database: Postgres cluster on PlanetScale with drizzle-orm
- Binding: Configured via Cloudflare Dashboard (PlanetScale integration) and added to wrangler.jsonc
- Framework: Next.js 16 using @opennextjs/cloudflare

Wrangler Configuration:

  "hyperdrive": [
    {
      "binding": "HYPERDRIVE",
      "id": "xxxxxxxxx",
      
      // Optional. Can be used to connect to a local database for local development with `wrangler dev`
      "localConnectionString": "my-postgres-string"
    }
  ]

  "hyperdrive": [
    {
      "binding": "HYPERDRIVE",
      "id": "xxxxxxxxx",
      
      // Optional. Can be used to connect to a local database for local development with `wrangler dev`
      "localConnectionString": "my-postgres-string"
    }
  ]

The Issue:
In local development, everything works as expected with localConnectionString. However, in production, env.HYPERDRIVE.connectionString appears to be undefined.

The only way I can get the Worker to connect to the database is by adding a Secret named CLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_STRING_HYPERDRIVE containing the connection string. Without this Secret, the database connection fails.

drizzle index.ts

import { getCloudflareContext } from "@opennextjs/cloudflare"
import { drizzle } from "drizzle-orm/postgres-js"
import * as schema from "./schema/index"

export function getDb() {
  const { env } = getCloudflareContext()
  const connectionString = env.HYPERDRIVE.connectionString

  const db = drizzle(connectionString, { schema })

  return { db }
}

import { getCloudflareContext } from "@opennextjs/cloudflare"
import { drizzle } from "drizzle-orm/postgres-js"
import * as schema from "./schema/index"

export function getDb() {
  const { env } = getCloudflareContext()
  const connectionString = env.HYPERDRIVE.connectionString

  const db = drizzle(connectionString, { schema })

  return { db }
}

My Question:
Why is the connection string not being automatically injected via the Hyperdrive binding in production? I assumed the binding would handle the connection string internally without requiring a manual Secret (especially one using the "LOCAL" naming convention). Is there a configuration step I am missing for production?

Hyperdrive with postgres and Planetscale

Workers

  "hyperdrive": [
    {
      "binding": "HYPERDRIVE",
      "id": "xxxxxxxxx",
      
      // Optional. Can be used to connect to a local database for local development with `wrangler dev`
      "localConnectionString": "my-postgres-string"
    }
  ]

  "hyperdrive": [
    {
      "binding": "HYPERDRIVE",
      "id": "xxxxxxxxx",
      
      // Optional. Can be used to connect to a local database for local development with `wrangler dev`
      "localConnectionString": "my-postgres-string"
    }
  ]

import { getCloudflareContext } from "@opennextjs/cloudflare"
import { drizzle } from "drizzle-orm/postgres-js"
import * as schema from "./schema/index"

export function getDb() {
  const { env } = getCloudflareContext()
  const connectionString = env.HYPERDRIVE.connectionString

  const db = drizzle(connectionString, { schema })

  return { db }
}

import { getCloudflareContext } from "@opennextjs/cloudflare"
import { drizzle } from "drizzle-orm/postgres-js"
import * as schema from "./schema/index"

export function getDb() {
  const { env } = getCloudflareContext()
  const connectionString = env.HYPERDRIVE.connectionString

  const db = drizzle(connectionString, { schema })

  return { db }
}

Hyperdrive with postgres and Planetscale

Hyperdrive with postgres and Planetscale

Similar Threads

Similar Threads

Similar Threads