im also on pages so that makes it extra tricky
im also on pages so that makes it extra tricky
GPages seems each time in late of features, we've switched to isolated workers since many months.
I've read in a blog article may be 1 or 2 years ago that the main goal is to merge the Pages & Workers, this will then be better.
I've read in a blog article may be 1 or 2 years ago that the main goal is to merge the Pages & Workers, this will then be better.
GWe've created our SQL structure tables/fields and all requests in the exact same way as if the DB will be isolate per user or common to everybody, so you then only have to adjust the DB selector to choose what's the best for you when you go in production
CHey everyone, I wrote a package to use the D1 API outside Workers: https://github.com/Cretezy/d1-api
GitHub
Interact with the Cloudflare D1 API outside of Cloudflare Workers - GitHub - Cretezy/d1-api: Interact with the Cloudflare D1 API outside of Cloudflare Workers
CIt uses the Cloudflare API to run queries directly without using bindings. Useful if you need to interact with D1 in a non-live manner (e.g. scripts, since the D1 HTTP API has latency).
CIt also supports tagged templating, e.g.
d1api.first`SELECT * FROM users WHERE id = ${id}`
PCan confirm that this is awesome, use it a lot for my game
CYes, if I have time. Open to contribution!
CI will likely support custom URLs, to proxy through Workers for better performance. But it'll be optional still
GHi! I'm worries about the meta.last_row_id, the name suggest it's the actual last rowid, and may be not the rowid assigned to the submitted INSERT query.
I'm afraid about concurrency, if multiple INSERT arrives at the same time, a last rowid could be different of the rowid assigned to the submitted INSERT query.
Could you please tell us if the meta.last_row_id is 100% guarantee it's the assigned rowid of our submitted INSERT query ?
I'm afraid about concurrency, if multiple INSERT arrives at the same time, a last rowid could be different of the rowid assigned to the submitted INSERT query.
Could you please tell us if the meta.last_row_id is 100% guarantee it's the assigned rowid of our submitted INSERT query ?
MIt’s only for the query you made.
PQuestion on best practice. I am writing a durable object such that I would like to have some log information about who has interacted with it. The object itself will contain a small bit of information but scales horizontally accross a lot of users.
I would like to store some log information about who is interacting with the object. Where in the cloudflare ecosystem should this live?
My instinct is D1, then appends become very easy, as does shrinking, trimming etc... I could write some batch codes that backup data to R2 on a semi-regular basis.
Because of the potential gerth of the log data, I don't think R2 makes sense as I would have to do a set/get on each interaction, which is a lot of memory to pull and set, which introudces a brittleness that I am not comfortable with.
I can't imagine that I am the person that have considered this recipe. How have other people solved it?
I would like to store some log information about who is interacting with the object. Where in the cloudflare ecosystem should this live?
My instinct is D1, then appends become very easy, as does shrinking, trimming etc... I could write some batch codes that backup data to R2 on a semi-regular basis.
Because of the potential gerth of the log data, I don't think R2 makes sense as I would have to do a set/get on each interaction, which is a lot of memory to pull and set, which introudces a brittleness that I am not comfortable with.
I can't imagine that I am the person that have considered this recipe. How have other people solved it?
MWrite to a Queue and then store somewhere asynchronously? Where you store will highly depend on how you want to consume that “log” information, and what it represents.
PYep, "how you want to consume that information"
If I want to stay in the Cloudflare ecosystem, the only option that includes append is D1, right? I could write to an external service, but would prefer to keep it all in one place.
If I want to stay in the Cloudflare ecosystem, the only option that includes append is D1, right? I could write to an external service, but would prefer to keep it all in one place.
MYou can write objects to R2, append to a D1 table, add to an ordered KV list… again, it will highly depend on how you want to access that information. If you just want to run SQL queries, then D1 is a great fit.
MI would think less about “append” and more about accessing/query patterns.
PRight, but to write an entry to R2, or KV, I would have to pull the entire value, write to it, and then store it back in the store. With log data, which can grow very quickly, it seems that introducing that much data to the mix would hit a memory ceilng at some point.
GLogs Engine gives you the ability to store your logs in R2 and query them directly.
POoh, I didn't know about that.
MStep back a second: how do you want to query it or access it? Many tools can read multiple R2 objects. I don’t think “append to a single object” is the problem here.
PSo it is engagement data, a user would interact with a product, or a post and I want to capture that for the person that owns that user. Once that data is caputred, I will want to aggregate the values into consumable insights:
Durable objects don't have a ceiling in terms of storage per class so... I could write to a node there and then if I ever get to the ElasticSearch plan I could do a direct import from JSON.
- Most active
- Least active
- Average Order Volume
- Total purchases
- Lapsed buyers
- Lapsed viewers
- Most active by chanel
- Channel volume
Durable objects don't have a ceiling in terms of storage per class so... I could write to a node there and then if I ever get to the ElasticSearch plan I could do a direct import from JSON.
PI think I am considering memory because I have burned in the past by not considering it. (not at cloudflare).
Logs looks awesome and maybe exactly what I am looking for.
Logs looks awesome and maybe exactly what I am looking for.
PThis has been a helpful exchange this morning, thank you.
PIt could eventually write directly to Elastic
PAnd by that time, CloudFlare will have already implmented Elastic for me under my workers plan.
FHello! I've checking on the doc for the best way to add a new column in a table of my database, but I don't seem to find anything. My table already contains data, and I would like to add two new columns without altering the data already in my table, is there a place where I can find how to do this?
JHi - is it normal for the very first SELECT from a cold started worker to take ~300ms to return a single row from a D1 table with just one row and two columns? Subsequent SELECT queries are ~25ms. This timing is specifically just the D1 query, not the total worker run time.
RIs there some kind of alert when we are approaching the max DB size for D1? I launched a link shortener for my https://d4planner.io site, and I'm basically prepending shortened links with
1- to denote which DB it hits, so I can rotate through if I hit the max size.
IIs there a specific reason why you went with D1 for a link shortener?
IPS: it's a really high number of links at 2GB...
RSeemed like it would be a cheaper option than KV
IInteresting, never really did the calculations there. Is it? 
RRIOh yeah, you are right, if you read one row per request (or probably two, given index + table) it's definitely cheaper.
IYou are not getting global caching, at least for now.
RYeah my table is basically just ID - path
RAnd I have an index on path
RI'm using caching via the hono middleware
ROn the link creation endpoint, as well as the shortened redirector
IWhy?
RSo if someone has already created a build I don't have two different short urls map to the same long url
RThough that could probably be minimized with the cache