Hi, I am having troubble setting up drizzle with the local d1 database, when running `bun drizzle-ki
Hi, I am having troubble setting up drizzle with the local d1 database, when running
bun drizzle-kit migrate
i receive the following error:
I attach my drizzle.config.ts and wrangler.toml below.
Anyone have any ideas on how i could fix my error?18 Replies
drizzle.config.ts
toml
I want to write a backend accounts API using Workers and D1, but using Rust instead of TypeScript. I see some ORMs listed at https://developers.cloudflare.com/d1/reference/community-projects/ for TS, but I don't see anything Rust related. Are there any I can look into? I'm basically very unsure how to dive into building this tech stack. It would also be nice to take advantage of Rust's ecosystem with libraries like Axum, is that feasible?
For those hitting this, and other similar errors, we’ve escalated and are told the team are actively investigating.
I am trying to get them to post something more official, but hopefully we’ll see a real resolution soon.
Unknown User•4mo ago
Message Not Public
Sign In & Join Server To View
Hi, I wanted to ask you a question: should I push the database_id to the repository? If not, how do I put it as an environment variable? I can't find it in the documentation.
The ID is safe to commit
ty i thought it was sesitive data
Everything in the wrangler.toml is safe to commit. The only thing would be environment variables which are sensitive. Those should be stored as secrets
Hi there! I'm doing a usage counter with max cap. What would be the best way to increment the counter that I can detect if it has reached the threshold without going over?
I would look at durable objects
Thanks! I was try to avoid durable objects because it will double the work (durable object logic, durable object management). I was able to to it with sqlite trigger with
RAISE
Unforunately I've experience this same error as well. Had to execute trigger creation manually via wrangler.We've closed the incident.
Here's what happened: we rolled out a fix for rare cases where D1 DBs weren't booting up successfully last week. This fix uncovered a bug from an update we released months ago, and caused a small percentage of requests to fail (roughly 1 error for every 22.5k requests) and return an error of
Internal error in D1 storage caused object to be reset
.
We have rolled back the update from months ago, and the errors have stopped as of 2024-09-04 21:55 UTC🙏
Hey Cloudflare team,
I saw that the current limit is 10GB per database, but we need to store data for about 200 million users, which would require something like 200GB. With the 10GB limit, we can only fit data for around 10-20 million users.
Are there any plans to increase the limit, or is there any way to upgrade to larger storage? Just trying to figure out the best approach for our project.
Thanks in advance!🙏
If you're set on storing that data in a single database, we'd recommend using Hyperdrive instead
Unknown User•4mo ago
Message Not Public
Sign In & Join Server To View
D1 is built around Cloudflare's network, which is really efficient at loading lots of small files really quickly - we'd offer bigger DBs but the cold starts would be brutal