So, it looks like smart placement was re-enabled 30 mins ago and yeah, so far it doesn't have enough
So, it looks like smart placement was re-enabled 30 mins ago and yeah, so far it doesn't have enough requests
Syeah i did it (a few times in fact) to see if it reappears
Sthe other worker hadn't hat it reenabled and doesnt have it either
WI can check that one too, what's it called?
Sworker-customer-***
Slast deployment there was a month ago
WIt looks like that also has pretty minimal traffic. looks like it was placed on the 13th and then not on the 15th - let me see what changed
SThx! The problem is each of our tenants won't have much traffic. we are a cloudbased cash register provider, so we only have a limited amount of users per tenant
WOk I see what changed.. figuring out why
WOk yep, looks like an issue our side - gonna let the team know!
Thanks for reporting, we'll get it fixed!
Thanks for reporting, we'll get it fixed!
S<3 Thank you!!!
Kcan someone help me with this. I'm trying to connect vitest with D1 local generated by wrangler dev, but it's not working, I use Vitest-pool-workers to do it with this configuration:
and to ensure I tried to show in the logs like this
and it's show undefined, it just show some data when I run wrangler dev,
and to ensure I tried to show in the logs like this
and it's show undefined, it just show some data when I run wrangler dev,
AIs it possible to increase the 10 gb Limit d1 has currently?
1
Cloudflare Docs
Cloudflare also offers other storage solutions such as Workers KV, Durable Objects, and R2. Each product has different advantages and limits. Refer to Choose a data or storage product to review which storage option is right for your use case.
AYes, already read that, but was not sure if applicable to the db limit in General too. Thanks!
1I think most of the limits can be increased, its mostly about being able to justify your use case. If you need the 10GB DB limit raised, you would probably want the 250GB account limit raised too?
ADon‘t know yet, just exploring possibilities. And if there’s no hard cap that can’t be raised, d1 seems good to go 
1If you are storing close top 10GB in a single DB, there is probably a better way to store/split the data up. If you do ever need the limit increased, I'd be asking way in advance
WHi all. Does anyone know/heard if there are any plans to run D1 in
sam? It just says it's not available but no comments on weather there are plans or not. (https://developers.cloudflare.com/d1/configuration/data-location/#available-location-hints)
WHeyo, sorry for not getting back sooner - just lots of other stuff going on
Eng released a fix and I can see your Workers being placed again
Eng released a fix and I can see your Workers being placed again
SThx! I can confirm for our test tenant, but not the prod one. Still says insufficient invocations
after testing, the responsetime of our test tenant is back to the original ^^
after testing, the responsetime of our test tenant is back to the original ^^
KHey, where do I find D1 repository? Couldn't find it on GitHub.
JFor what specifically? You'll find some of D1 source in the
workerd repo like https://github.com/cloudflare/workerd/blob/main/src/workerd/util/sqlite.c%2B%2B, but if you're new to D1, the Getting Started guide is going to the best place to start: https://developers.cloudflare.com/d1/get-started/
THello everyone,
Quick question. Is D1 a suitable backend database for a financial wallet web application? i.e. ensuring consistency across users funds balances / withdrawing funds and depositing funds reflect consistently across all users of the wallet app. Is D1 sufficient for this use case? or will i need a Postgres db for example?
Thanks,
Quick question. Is D1 a suitable backend database for a financial wallet web application? i.e. ensuring consistency across users funds balances / withdrawing funds and depositing funds reflect consistently across all users of the wallet app. Is D1 sufficient for this use case? or will i need a Postgres db for example?
Thanks,
KSpecifically for the D1 engine. Afaik it's an extension of SQLite engine.
LFrom a consistency perspective, D1 is on par with Postgres. Reliability and recoverability are more a function of how each is hosted and Cloudflare is well above average on this front. The biggest difference is scaling both in size and throughput. D1 maxes out at 10GB. Postgres DBs can be TBs. Similarly, D1 also has significant throughput scaling limitations compared to Postgres and I suspect that will continue even after D1 is upgraded to support read replicas.
JI remember reading a message about "unlimited read throughput" once read replicas arrive. But writes would still have the same throughput limitations as it has today.
LThat's good news. I hadn't read that.
Eis d1 down? i keep getting auth errors
E@Walshy ?
FPlease do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.
VHi y'all, what's the latest news on transaction support?
I'm using the Drizzle ORM and transactions don't work there: https://github.com/drizzle-team/drizzle-orm/issues/2463
I'm using the Drizzle ORM and transactions don't work there: https://github.com/drizzle-team/drizzle-orm/issues/2463
GitHub
What version of drizzle-orm are you using? 0.31.1 What version of drizzle-kit are you using? 0.22.2 Describe the Bug When trying to execute a transacction with cloudflare d1 adapter it throws the f...
Ehow do i force a schema change? I added autoincrement like a noob
Mhelpme
IThis is the Cloudflare D1 channel, unrelated to MySQL. I'd recommend positing in #off-topic, but at the same time, there's not much we can do to help with a single screenshot of a MySQL process using a lot of resources.
Rhi. i've been trying to make d1 work in rust with bigint (i64) data types, and i keep getting this error: Error: Error: D1_TYPE_ERROR: Type 'bigint' not supported for value '300' - Cause: Error: D1_TYPE_ERROR: Type 'bigint' not supported for value '300'. what am i missing?
LD1 is based on SQLite, so these are the types you can use: https://www.sqlite.org/datatype3.html
Not sure how Rust is involved in your code, but
How are you using Rust, are you using the D1 Worker binding with Rust WASM, or something else?
That error is coming from the D1 Worker binding, so it expects JS types.
Not sure how Rust is involved in your code, but
bigint is not a valid SQLite type and gets converted to one of the native ones, in this case INTEGER.How are you using Rust, are you using the D1 Worker binding with Rust WASM, or something else?
That error is coming from the D1 Worker binding, so it expects JS types.
Ryes, i am using d1 worker with rust and i have a i64 variable, i am trying to bind to an Integer column when i get this error. Here is the code and schema:
Drop Table Test;
CREATE TABLE IF NOT EXISTS Test (
Id TEXT PRIMARY KEY NOT NULL,
Value INTEGER NOT NULL
);
Drop Table Test;
CREATE TABLE IF NOT EXISTS Test (
Id TEXT PRIMARY KEY NOT NULL,
Value INTEGER NOT NULL
);
Rlet d1 = ctx.env.d1("DB")?;
let statement = d1.prepare("INSERT INTO Test (Id, Value) VALUES (?1, ?2)");
let v: i64 = 300;
let query = statement.bind(&["abc".into(),
v.into()])?;
let result = query.run().await?;
console_log!("result: {:?}", result.success());
let statement = d1.prepare("INSERT INTO Test (Id, Value) VALUES (?1, ?2)");
let v: i64 = 300;
let query = statement.bind(&["abc".into(),
v.into()])?;
let result = query.run().await?;
console_log!("result: {:?}", result.success());
Ri think i figured this out - i have to convert everything to string on rust side - and then despite things being strings, d1 interprets them correctly as integer of varying size.
LAre you sure they are written as integers though? SQLite non-strict tables accept anything you give them regardless of the column type. I would suggest converting the i64 into a normal integer before passed to the statement bind call. Maybe this works, and you will keep them as integers.
CSuper weird issue but could it be that the Cloudflare D1 export via
The first issue is that datetime fields aren't put under quotes. After fixing that via multi-cursor editing I'm getting the following error
I know D1 is still new but I would expect that I could import the dump I exported via it.
npx wrangler d1 export dharmaradio --remote --output=dump.sql creates a dump which can't be imported again via npx wrangler d1 execute dharmaradio --remote --file=dump.sql.The first issue is that datetime fields aren't put under quotes. After fixing that via multi-cursor editing I'm getting the following error
{"D1_RESET_DO":true} . I know D1 is still new but I would expect that I could import the dump I exported via it.
C40mb but that doesn't explain why the export can't be imported
CNo, it first fails on parsing the sql because of the missing quotes around the dates. Once i fixed that it succeeds parsing the sql and then breaks with the d1_reset_do error.
I wrote a script to chunk the inserts in the dump so hopefully that works out but the export 100% has some issue
I wrote a script to chunk the inserts in the dump so hopefully that works out but the export 100% has some issue
G(In this screenshot
ENAM_OBJECTS is an empty database in a closer pop than ENAM_USERS. Same with the WNAM databases)GIt's especially apparent when on average it's this drastic
DI need to specify where my D1 database will be located. As in, it needs to be in Canada. Is it possible? I can only see location hints but I don't think that's enough due to legal reasons
ICorrect, location hints won't be enough if it's for compliance. And I don't believe D1 supports Jurisdiction Hints like R2 (and even if it did, there's no Canada jurisdiction at the moment).
DThat’s very unfortunate. I love the d1 experience, but yeah… compliance is compliance 
LNo, you cannot control more fine-grained locations than regional location hints.
