Immutable solution version
Error: bind message supplies 1 parameters, but prepared statement "" requires 0
Complete solution
Serverless: error: bind message supplies 1 parameters, but prepared statement "" requires 0. The verified fix is Fix: [jawj (maintainer)]: Fixed in driver 0.4.23. Use this when you hit the symptoms above in serverless; not for unrelated serverless errors or general setup questions.
TL;DR
Fix: [jawj (maintainer)]: Fixed in driver 0.4.23.
The error
Adding one or more parameters to the query cause the error: `NeonDbError: db error: ERROR: bind message supplies 1 parameters, but prepared statement "" requires 0` when `neonConfig.poolQueryViaFetch = true`Fix
- [jawj (maintainer)]: Fixed in driver 0.4.23.
Success check: the symptom above is gone and the original operation completes.
When to use
- You hit this exact symptom in serverless.
- You want the verified fix without digging through the thread.
When not to use
- A different error in serverless, even a similar-looking one.
- General serverless setup or credential questions.
Compatibility
- Serverless (neondatabase/serverless)
Variant phrasings
- How to fix "error: bind message supplies 1 parameters, but prepared statement "" requires 0" in serverless
- serverless: error: bind message supplies 1 parameters, but prepared statement "" requires 0
- problem: bind message supplies 1 parameters, but prepared statement "" requires 0
Source
- https://github.com/neondatabase/serverless/issues/28
Evidence
Asked in gh:neondatabase/serverless#28 (https://github.com/neondatabase/serverless/issues/28): Error: bind message supplies 1 parameters, but prepared statement "" requires 0. The issue report: Issue neondatabase/serverless#28 (closed, 9 comments): ## Steps to reproduce Adding one or more parameters to the query cause the error: NeonDbError: db error: ERROR: bind message supplies 1 parameters, but prepared statement "" requires 0 when neonConfig.poolQueryViaFetch = true
neonConfig.poolQueryViaFetch = true
const pool = new Pool({ connectionString: env.DATABASE_URL })
const result = await pool.query(`SELECT * FROM "Client" WHERE id = '$1'`, [
"xxxxxxxxxxxx",
])Expected result
The same response as if the parameter were set inline like: const result = await pool.query('SELECT * FROM "Client" WHERE id = "xxx The verified answer: [jawj (maintainer)]: Fixed in driver 0.4.23. Drizzle calls an odd hybrid form query({ text: 'SELECT ...' }, [...]) - neither the usual query(text, values) nor query({text, values}) - which the HTTP driver's poolQueryViaFetch` path mishandled, producing the bind-message error. Reporter confirmed it works in 0.4.23.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_MpobzEgRlo9NlVb6WCN-Ig" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Error: bind message supplies 1 parameters, but prepared statement "" requires 0 <span>— Vectle</span></a>