It’s a planned feature, but it doesn’t exist yet
It’s a planned feature, but it doesn’t exist yet
MExactly the same query from different locations.
MCan we know if it's planned for Q1 or more into the future?
MYeah.. Time to refactor everything since I counted with read replicas since their documentation mentions them...
TI might have a tool that helps a bit with managing the env/config
Tloads config like dotenv but also has validations, and a nice wrangler integration - https://dmno.dev/
Tdang thanks! i’ll check it out
Tthe cloudflare integration is brand new, so happy to help and work through any issues 
T“Being able to see all of these values and which one is currently active will save you tons of headaches”
huge. im tired of “zero config” “common sense” “best practice” “no code” etc
huge. im tired of “zero config” “common sense” “best practice” “no code” etc
Oit works for me
AI was trying out the d1 get started guide and the first command to create a d1 project doesn't work. I tried using npm and it throw a 404 Error. I tried using npx also but a similar error happened, although a little bit different as you can see on the terminal. I tried installing create-cloudfare and it also didn't work. What do I need to do to make it work?
JIt looks like you typo’d cloudflare to cloudfare
AOh, what a rookie mistake haha thanks for pointing it out
KIf I got multiple databases in local, how can I get the exact SQLite path for specific database ?
IHey i have db per user case, and now i need to check it with cron if a user have some event scheduled to do some processing and send emails. Is there any smart way of querying all databases at once?
Jsadly not really. If we had dynamic bindings this'd be easier, which were a "before GA" promise as per https://canary.discord.com/channels/595317990191398933/992060581832032316/1164575886520090684, but still nothing to report there.
Ithanks
ZRead only replicas are coming before the end of the year too! 
:COPIUM:
:COPIUM:
Mwhere did you see that anouncement?
ZIn one of the blog posts 
1Durable Objects would be the best way forward here
Athe math aint mathing
HThat might be because the system that powers account-level analytics may be a bit behind the actual values
Aif thats the case, then that would be like a year behind
HWeird
Athat 3gb db has been well past that size for a loooong time
Anot the end of the world, but a bit odd 
AIs it possible to use a backend framework like fastify in a wrangler/d1 project? And what about postgres to make queries?
KI’m encountering D1 slow response, like 500ms+, but my table only have 10 rows, the database is under APAC region. Is that expected?
KRequest without D1 fetch, around 30ms. With D1 fetch around 600ms
WWhere is your worker invoked?
WAnd are you using smart placement?
KAlso under APAC
Kdefault placement
ILighter Prisma is in the works.
The Kysely gap you described is solvable today-ish with plugins, and possibly in the future with some new APIs (but without turning the library into yet another ORM.)
The Kysely gap you described is solvable today-ish with plugins, and possibly in the future with some new APIs (but without turning the library into yet another ORM.)
KAlso when I create D1, if I don’t specific region, it will create in North America, but it’s obviously far away from APAC. Is this recommended?
FHello everyone, does D1 have a boolean value? If not, what are the best practices for implementing boolean values on D1?
F
FAh, got it.
AHey all 
I'm a massive Cloudflare advocate in my big organization, and we use it heavily. So far we haven't been using D1 as we have no need. But I've started using it on a side passion project of my own.
So far everything works how I would like it, except that the Response time for basically any query (even the most simple ones) are very high.
I have a worker which serves as my API layer, and it calls the D1 internally. Every request takes over 2-3 sec to respond.
What is your experience with D1 response times?
Also to mention, the DB is very small ~12kb in total.
I'm a massive Cloudflare advocate in my big organization, and we use it heavily. So far we haven't been using D1 as we have no need. But I've started using it on a side passion project of my own.
So far everything works how I would like it, except that the Response time for basically any query (even the most simple ones) are very high.
I have a worker which serves as my API layer, and it calls the D1 internally. Every request takes over 2-3 sec to respond.
What is your experience with D1 response times?
Also to mention, the DB is very small ~12kb in total.
JThat seems to align with what others are reporting, depending on network latency, types of queries, db location, etc. I would be wary of using D1 in production though until there's some more guidance around error rates and types of errors, since they do seem to happen more than would be reasonably expected: https://github.com/cloudflare/cloudflare-docs/issues/18485
AInteresting. I've just joined Disc here, and I'm reading through history, where I'm seeing people having the same problem I'm having.
@James do you have some recommendation on what works well as a simple DB together with Workers?
@James do you have some recommendation on what works well as a simple DB together with Workers?
JI'd go with Postgres via https://neon.tech/ if you want something more featured than SQLite - you can pair it with Hyperdrive for some impressive latency/query times, or https://turso.tech/ if you want SQLite which I've heard good things about
AOk great, I will try it out. I might go with SQLite first as I've already built most of the queries/seeds etc. And I really need the most basic of stuff.
I appreciate the recommendations.
I appreciate the recommendations.
Ganyone using raw sql? or everyone using an ORM like drizzle? just curious. 
II previously used raw SQL and I moved to Drizzle. I still try to use Drizzle as close to raw SQL as I can (I use the query builder not their
db.query wrapper) but IMO it's very handy to be able to construct SQL with standard JS/TS functions rather than string interpolation.WDrizzle's functions are fine for simple queries. Any more advanced and they're messy and limited
WLuckily most queries usually are simple
