Wreturn "404 Not Found"
SWeird, also does D1 not support ON CONFLICT? You can have a single query using this, instead of the current 3
WA single query still returns the same result. There is too little information about updates in the official documents. I’m not sure if I wrote it correctly.
MD1 doesn't throw 404 - are you hitting the right URL of your API?
MAre you making a POST request? Your Hono route is
app.postOkay, thank you everyone. There is an extra bracket in the code, but the editor did not remind me.
MD1 is Cloudflare’s native serverless database. D1 allows you to build applications that handle large amounts of users at no extra cost. With D1, you …
MInteract with Cloudflare's products and services via the Cloudflare API
SIs there any way to interleave two tables on disk? I have a table that has a 1 to many relationship with another table. I'm never going to query the "many" table to ask if it connects to the "one" table, always the other way around. I'd like to tell Cloudflare that they can optimize it by keeping the records from the 1 table next to the corresponding records from the many table by interleaving the rows on disk. That way it only needs to pull 1 disk block up when I query for data. Is this possible?
SAlso, any way to bump up the 2 GB limit? Ikr it's not production ready, but I'd like to use it for a purely non-profit idea and I'm not sure if I'll stay under that limit
KD1 is built on SQLite, so this is only possible if SQLite itself contains such a feature. I don't think it does. But at the same time, I suspect this kind of feature would not have so much benefit given we're running SQLite backed by a local SSD. It'd be more important for a distributed database that might split data across many machines, but D1 doesn't do that.
SIt doesn't do that? I thought the big advantage of d1 is that it's present at all your cdns. Does it just replicate the whole db everywhere?
ID1 is currently single location (either close to where you are when you create your DB, or in a geographic area of your choosing selected when you create the DB).
IIn the future there will be read replication support. But for now it's single location.
KSmart Placement will always run your Worker near the D1 DB
MI would use integers
SGood to know. Most of my data can also be modeled as key-value pairs so I'll use that + hyperdrive.
INote that Smart Placement places the Worker near the D1 DB. You'll still have to talk to the Worker back in Canada (in your example).
ZI would recommend ensuring R2 and D1 are in the same region, then enabeling smart placement.
MSmart placement should automagically do that for you (as in decide the optimal place to put the Worker)
ZIt wouldn't put R2 and D1 in the same place, right?
KWe are working on replication for D1, but even when it is replicated, each replica will store the entire database, so there's no need for a query to gather data from multiple machines. We might later add support for sharding, which puts different data on different machines, but we'll likely do this based on an explicit shard key provided by the application, so you'll be able to control which data lives together using shard keys rather than by interleaving tables.
UI dont even want to know what the cost of D1 would be if it was every datacenter 
RI created a database and chose a location in asia pacific. But why is the latency still so high? It even took up to 1 minute just to view the home page of my web application.
I am in Indonesia and My Web Application targets Users from Southeast Asian Countries.
I have selected the right location for My Database but the Latency is still so High. I don't know where in the Asia Pacific Region the D1 Data Center is located.
I am in Indonesia and My Web Application targets Users from Southeast Asian Countries.
I have selected the right location for My Database but the Latency is still so High. I don't know where in the Asia Pacific Region the D1 Data Center is located.
H+1 for jurisdictional control over those shards 
GThe temporary solution is to PATCH the settings of your worker to attach new bindings ( REST API ) and then you can uses D1 through without the REST API
MThese are still bindings.
GIndeed, I've misread the question of @Mustafa Akın
Can you share with us any news about your future solutions?
Can you share with us any news about your future solutions?
MNot yet. We’ve shared a lot here already - it’s something we’re working on and will be part of/ahead of GA.
KD1 is SQLite, and doesn't really have the concept of users that you'd apply RLS to anyways.
KI'm not sure what you mean by that.
KYou use the REST API or bind a Worker to the database.
Mit's up to you to add application logic to show data based on authentication/authorization
MI recommend you go through the getting started guide to understand how it works: https://developers.cloudflare.com/d1/get-started/
H(FYI for the discussion above this is how you PATCH extra bindings into a worker—cheers Max!)
MIs there a way to "reset" a database (ie. get it into the same state as if just created). This would be helpful with prototyping where I would like to reset the database and run the single migration I have that I'm editing. Currently, I'm deleting the database, creating another a new one with the same name, binding it to the pages app, updating the database id in the wrangler.toml, and finally applying the edited migration. Would be great to simply reset the database and then apply the edited migration. With local dev, I delete the
.wranglerI just throw a
DROP TABLE IF EXISTS...
CFor anyone that’s used D1, what’s the performance look like?
CI’m using turso and planetscale right now and I’m thinking about making the switch
JI was using Planetscale and switched to D1. much lower latency (improved about 50-100ms) for most areas I tested against.
Faster DB queries too but planetscale wAs pretty fast. Sorry, can't recall numbers.
Faster DB queries too but planetscale wAs pretty fast. Sorry, can't recall numbers.
CYeah I’m thinking latency will be the biggest thing given that I usually use pages
CBut I’m just worried about the query time tbh
Mquery time is fast with an index, getting data out rapidly is still a
//TODO
CD1 DBs are only accessible via bound workers or via the API/API Tokens you make. The only Workers that can access them are ones which are bound. IP Restrictions would be something you could do in the worker/firewall level
CIt's not like they're normal SQL DBs that you can connect to externally, D1 is based on SQLite, no connection strings
V@Nico What type of access controls are you interested in from a bound Worker itself?
AIs there a way for me to export my entire D1 to a file/something so I can put it into reporting tools like PowerBI etc?
A gives me the error