Skip to content

Conversation

@Quatton
Copy link
Contributor

@Quatton Quatton commented Mar 11, 2024

I followed through the Drizzle recipe in the docs and it seemed like the database migration did not go through with the following error:

[nitro] [unhandledRejection] Error: D1_ERROR: A prepared SQL statement must contain only one statement.
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at <anonymous> (C:\Users\Atom\Documents\GitHub\careear\server\plugins\migrations.ts:24:1)
    at getBindingsProxy (C:\Users\Atom\Documents\GitHub\careear\node_modules\@nuxthub\core\src\module\runtime\bindings.dev.ts:57:1) {
  [cause]: Error: A prepared SQL statement must contain only one statement.
      at D1Database._sendOrThrow (cloudflare-internal:d1-api:67:24)
      at async D1PreparedStatement.run (cloudflare-internal:d1-api:172:29) {
    [cause]: undefined
  }
}

I'm not sure how this happened because it was perfectly fine until recently, likely due to a dependency version (?). However, the trim() method fixed the error so I propose a small change in the docs. WDYT?

@vercel
Copy link

vercel bot commented Mar 11, 2024

@Quatton is attempting to deploy a commit to the Nuxt Labs Team on Vercel.

A member of the Team first needs to authorize it.

@vercel
Copy link

vercel bot commented Mar 11, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nuxthub-remote ✅ Ready (Inspect) Visit Preview Mar 11, 2024 9:47am

@atinux atinux merged commit 6f5cc58 into nuxt-hub:main Mar 11, 2024
@atinux
Copy link
Contributor

atinux commented Mar 11, 2024

Thank you!

@cloudflare-workers-and-pages
Copy link

Deploying nuxthub-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 012b2ea
Status: ✅  Deploy successful!
Preview URL: https://345e262f.nuxthub-module.pages.dev

View logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants