K
KI also changed other sql command, but not working as well
Myou're missing quotes around the id, should be
WHERE id = '...'not works
Msingle quotes*
Kno ��
Mwait why is it form-data
MInteract with Cloudflare's products and services via the Cloudflare API
Khmm OK, so raw works
Zi see there are two tables in my database
but i dont know what is the command to get the name of each table so i can confirm.
when i checked in the dashboard, it says 2 tables but shows only one table.
how to get the table name?
formsnpx wrangler d1 info formsbut i dont know what is the command to get the name of each table so i can confirm.
when i checked in the dashboard, it says 2 tables but shows only one table.
how to get the table name?
Dwondering if the 10GB disk limit would be increased down the line or is that something unlikely to happen?
DThx for that, that’ll be perfect for my use case.
WHeyo! I couldn't find a solution for seeding local D1, so I wrote a workaround. Let me share it here for someone who wants to seed local D1 like me.
https://www.npmjs.com/package/seed-d1
https://www.npmjs.com/package/seed-d1
npm
Workaround for seeding against local Cloudflare D1 database.. Latest version: 0.0.1, last published: 36 minutes ago. Start using seed-d1 in your project by running
npm i seed-d1
BSee the message that I'm going to quote in my next message
B^
BLast update from an employee that works on D1
Lhow do I create a Transaction in D1 using TypeScript?
HBatches are automatically run in transactions. You cannot create transactions manually
AI'm trying to restore my database (because an error caused it to be wiped) but every time i try, I just get "There was a problem restoring your database, please try again later."
any help with this would be highly appreciated
any help with this would be highly appreciated
AAnd I get this when trying it from wrangler:
BHello I have a question about future plans. Currently in the D1 limits page it says we can make
This makes me think that you guys are heading towards making it very easy to create databases, ie database per tenant, similiar to Turso. Is this correct?
50,000 (Workers Paid) / 10 (Free)This makes me think that you guys are heading towards making it very easy to create databases, ie database per tenant, similiar to Turso. Is this correct?
IYes. It's on the roadmap and actively being worked on but no timeline yet.
MIf i have an cloud app that has many customers, what is the Cloudflare architecture recommendation for stateful resources (like D1 and Queues)?
Is it better to stick with simple multi-tenancy (option-A), or is it better (or even possible) to use the Cloudflare API's to dynamically provision for each customer (option-B).
In the later case each customer would have their own set of D1 databases and Queues.
I don't see any doc or sample code demonstrating option-B?
Is it better to stick with simple multi-tenancy (option-A), or is it better (or even possible) to use the Cloudflare API's to dynamically provision for each customer (option-B).
In the later case each customer would have their own set of D1 databases and Queues.
I don't see any doc or sample code demonstrating option-B?
MOpps, appears a similar question was literally asked today!-)
It sounds like the answer to my question is that "option-B" is not currently supported?
I had the impression it may be, since there are API's that appear intended to dynamically provision resources?
https://developers.cloudflare.com/api/operations/cloudflare-d1-create-database
It sounds like the answer to my question is that "option-B" is not currently supported?
I had the impression it may be, since there are API's that appear intended to dynamically provision resources?
https://developers.cloudflare.com/api/operations/cloudflare-d1-create-database
ISo there are APIs to dynamically provision resources, but you can't bind them to use from a Worker without a redeploy of that Worker.
IThe "binding dynamically to the Worker" is what's on the roadmap/being worked on.
IYou can manually query D1 via the Cloudflare API but it's much slower than binding directly to a Worker and has very strict rate-limits (1200 calls per 5 minutes I believe?)
MGotcha, thx. I got ahead of myself when Claude 3.5 gave me this hallucination...
Is there a formal Issue publicly accessible to track this work?
thx
Is there a formal Issue publicly accessible to track this work?
thx
Mactively building it (during work hours anyway)
MMi'm not sure i would call that github project "dynamic" (maybe "cloudflare-gen-bindings")? Regardless - cool hack.
I wish there was an open discussions page to discuss requests and future direction?
Besides being able to dynamically create resources, it would also be nice to build some higher-level abstractions (at least for common usecases), to help simplify the management.
For example, it would be great if there was some form of higher-level "sharding" support that only required a resource to be configured with a "sharding key" (Example: A D1 "foobar" db shared by "customer_id"). That resource (D1, or Queue, or ...) would then require the shard-key to operate on it.
Under the covers Cloudflare would then manage "foobar" by appropriately creating a D1 instance when a new key is referenced, or finding/binding the instance when it does exist, and Migrations could also be done across the entire "foobar" cluster?
I wish there was an open discussions page to discuss requests and future direction?
Besides being able to dynamically create resources, it would also be nice to build some higher-level abstractions (at least for common usecases), to help simplify the management.
For example, it would be great if there was some form of higher-level "sharding" support that only required a resource to be configured with a "sharding key" (Example: A D1 "foobar" db shared by "customer_id"). That resource (D1, or Queue, or ...) would then require the shard-key to operate on it.
Under the covers Cloudflare would then manage "foobar" by appropriately creating a D1 instance when a new key is referenced, or finding/binding the instance when it does exist, and Migrations could also be done across the entire "foobar" cluster?
Mthat's roughly how we're designing d1 dynamic bindings
Mthe migrations story becomes "fun" with that though, since you can now make potentially millions of DBs, we don't want migrations to simultaneously wake up millions of DBs
MOK, great to know that more coolness is on the way.
To add another dimension of complexity - hopefully there is also some form of integration into "Gradual Deployments"?
https://developers.cloudflare.com/workers/configuration/versions-and-deployments/gradual-deployments/
Maybe that could be part of the story to ease the cost of migrations?
Btw, is there similar work in-progress to support dynamic binding (and sharding) for Queues?
Thx Max.
To add another dimension of complexity - hopefully there is also some form of integration into "Gradual Deployments"?
https://developers.cloudflare.com/workers/configuration/versions-and-deployments/gradual-deployments/
Maybe that could be part of the story to ease the cost of migrations?
Btw, is there similar work in-progress to support dynamic binding (and sharding) for Queues?
Thx Max.
