Any pricing updates? - Cloudflare Developers

© 2026 Hedgehog Software, LLC

More

Communities Docs About Terms Privacy

lukeed

L

lukeedOP•5/8/23, 5:24 AM

James

J

James•5/8/23, 6:38 AM

Nothing official yet. Functionally, there’s probably not going to be much difference other than your Cloud vendor of choice, which is going to come down to availability and pricing.

D1 is still very early and in alpha right now, but it’ll probably make the most sense to use alongside the rest of the Cloudflare stack.

Murder Chicken

M

Murder Chicken•5/8/23, 11:41 AM

Is there a best practice way to accomplish a query of this nature (with many more records) through D1's API?

INSERT INTO example_table (activity_id, user_id, status) 
VALUES 
  (2496, 1, 'AVAILALBE'),
  (2496, 1, 'NOT_AVAILABLE'),
  (2496, 2, 'AVAILABLE') 
ON CONFLICT DO UPDATE SET status = excluded.status;

INSERT INTO example_table (activity_id, user_id, status) 
VALUES 
  (2496, 1, 'AVAILALBE'),
  (2496, 1, 'NOT_AVAILABLE'),
  (2496, 2, 'AVAILABLE') 
ON CONFLICT DO UPDATE SET status = excluded.status;

Murder Chicken

M

Murder Chicken•5/8/23, 11:41 AM

Is it leveraging batchbatch with an array of objects or something of that nature?

Murder Chicken

M

Murder Chicken•5/8/23, 11:42 AM

Though I could not find a way to pass an array of data to batch... just an array of stmt.bindstmt.bind

ashutosh

A

ashutosh•5/8/23, 1:01 PM

Can we access the D1 database outside Cloudflare workers environment?

Farhian

F

Farhian•5/8/23, 3:27 PM

Hi guys, does D1 support the 'WITH RECURSIVE' syntax? Thank you!

lukeed

Llukeed Any pricing updates?

Epailes

E

Epailes•5/8/23, 3:29 PM

I think developer week is next week (or very soon) based on some comments staff have made, looks like it'll be shared then

Farhian

F

Farhian•5/8/23, 3:31 PM

@Sourabh.Sashank you need to be careful about SQL injection in those queries

Farhian

F

Farhian•5/8/23, 3:32 PM

You might want to consider preparing the queries and bind the params

Farhian

F

Farhian•5/8/23, 3:33 PM

Will do, thank you

Farhian

F

Farhian•5/8/23, 3:33 PM

it seems the recursive was added in mysql 3.8 and D1 is using 3.39.4 - so it should work

Farhian

F

Farhian•5/8/23, 3:36 PM

Thanks @skye_31

sourabh.sashank

Ssourabh.sashank Yeah. This is just the sample inner code to find out issue. We are doing vari...

Farhian

F

Farhian•5/8/23, 3:37 PM

awesome

Murder Chicken

M

Murder Chicken•5/8/23, 4:38 PM

Attempting to create a trigger in my schema.sql file results in a ERROR 9009: SQL prepare error: incomplete input [code: 7500]ERROR 9009: SQL prepare error: incomplete input [code: 7500] which I've seen reported elsewhere in here. Anyone experience this and get past it? Even the simplest trigger fails when trying to use the --file--file operator from wrangler to seed the live DB.

Murder Chicken

M

Murder Chicken•5/8/23, 4:39 PM

Removal of the trigger from the schema file and it works as expected but I was under the impression that sqlite triggers were supported (given, alpha).

Murder Chicken

MMurder Chicken Removal of the trigger from the schema file and it works as expected but I was u...

Matt Silverlock

M

Matt Silverlock•5/8/23, 6:01 PM

Can you share your syntax?

Matt Silverlock

MMatt Silverlock Can you share your syntax?

Matt Silverlock

M

Matt Silverlock•5/8/23, 6:01 PM

➜  npx wrangler@d1 d1 execute test-db --file 0000_initial.sql

🌀 Mapping SQL input into an array of statements
🌀 Parsing 25 statements
🌀 Executing on test-db (c020574a-5623-407b-be0c-cd192bab9545):

➜  npx wrangler@d1 d1 execute test-db --file 0000_initial.sql

🌀 Mapping SQL input into an array of statements
🌀 Parsing 25 statements
🌀 Executing on test-db (c020574a-5623-407b-be0c-cd192bab9545):

Matt Silverlock

M

Matt Silverlock•5/8/23, 6:01 PM

File = https://github.com/cloudflare/wildebeest/blob/main/migrations/0000_initial.sql

Matt Silverlock

M

Matt Silverlock•5/8/23, 6:02 PM

This all works, and has for a while, so I'm curious what you're doing differently here, or if your schema is too large or has some newline issue

Murder Chicken

M

Murder Chicken•5/8/23, 6:02 PM

This is the current bit that's breaking it...

CREATE TRIGGER 'updated_records_to_changelog' AFTER UPDATE OF 'status' ON 'availabilities'
WHEN OLD.status <> NEW.status
BEGIN
  INSERT INTO changelog (c_id, for_date, status_was, status_is) 
  VALUES (OLD.c_id, OLD.for_date, OLD.status, NEW.status);
END;

CREATE TRIGGER 'updated_records_to_changelog' AFTER UPDATE OF 'status' ON 'availabilities'
WHEN OLD.status <> NEW.status
BEGIN
  INSERT INTO changelog (c_id, for_date, status_was, status_is) 
  VALUES (OLD.c_id, OLD.for_date, OLD.status, NEW.status);
END;

Murder Chicken

M

Murder Chicken•5/8/23, 6:03 PM

Everything else in the file seems to be fine. Removal of this piece allows it to run.

Murder Chicken

M

Murder Chicken•5/8/23, 6:04 PM

Wrangler 2.19.0

Murder Chicken

M

Murder Chicken•5/8/23, 6:06 PM

Of further note, this works locally.

Murder Chicken

M

Murder Chicken•5/8/23, 6:30 PM

@elithrar ok, I figured it out.

Murder Chicken

M

Murder Chicken•5/8/23, 6:30 PM

I had to add a single space after the BEGINBEGIN line.

Murder Chicken

M

Murder Chicken•5/8/23, 6:31 PM

Spaces anywhere else didn't matter (tried it with and without trailing spaces). As soon as I added a single space after the BEGINBEGIN the statement worked.

Murder Chicken

M

Murder Chicken•5/8/23, 6:31 PM

So definitely whitespace-related. Just super-hard to determine from the error message.

Murder Chicken

MMurder Chicken So definitely whitespace-related. Just super-hard to determine from the error m...

Matt Silverlock

M

Matt Silverlock•5/8/23, 7:41 PM

We definitely want to improve these over time.

Murder Chicken

M

Murder Chicken•5/8/23, 7:45 PM

Oof, yeah, debugging where these queries are failing is an exercise in frustration. Thanks for responding to assist though!

Murder Chicken

M

Murder Chicken•5/8/23, 7:57 PM

Is there any way to get more details on a [ERROR] Error: D1_ERROR[ERROR] Error: D1_ERROR that's happening on production but not locally?

Murder Chicken

M

Murder Chicken•5/8/23, 8:09 PM

Anyone ever encountered something like this:

  (error) Error: Error: Error 9000: exception caught in D1 core. unreachable RuntimeError: unreachable
    at wasm://wasm/00f5753e:wasm-function[4783]:0x31be54
    at wasm://wasm/00f5753e:wasm-function[4836]:0x322be4
    at wasm://wasm/00f5753e:wasm-function[4877]:0x32c7d6
    at wasm://wasm/00f5753e:wasm-function[237]:0x29575
    at wasm://wasm/00f5753e:wasm-function[4973]:0x34351d
    at Object.s2 [as query] (index.js:2418:157)
    at async Sqlite.query (index.js:3205:23)
    at async sqliteQuery (index.js:9409:29)
    at async index.js:9167:22

  (error) Error: Error: Error 9000: exception caught in D1 core. unreachable RuntimeError: unreachable
    at wasm://wasm/00f5753e:wasm-function[4783]:0x31be54
    at wasm://wasm/00f5753e:wasm-function[4836]:0x322be4
    at wasm://wasm/00f5753e:wasm-function[4877]:0x32c7d6
    at wasm://wasm/00f5753e:wasm-function[237]:0x29575
    at wasm://wasm/00f5753e:wasm-function[4973]:0x34351d
    at Object.s2 [as query] (index.js:2418:157)
    at async Sqlite.query (index.js:3205:23)
    at async sqliteQuery (index.js:9409:29)
    at async index.js:9167:22

Murder Chicken

M

Murder Chicken•5/8/23, 8:12 PM

I might be bumping up against some kind of cap with prepared batch statements. Is there a limit to how many you statements you can batch in one call?

Murder Chicken

M

Murder Chicken•5/8/23, 8:13 PM

Definitely possible. It's a lot of inserts.

Murder Chicken

M

Murder Chicken•5/8/23, 8:46 PM

That was it. Batching the batch seemed to get past it.

Murder Chicken

MMurder Chicken Definitely possible. It's a lot of inserts.

Matt Silverlock

M

Matt Silverlock•5/9/23, 12:11 AM

Curiously: how many? How long (in bytes) is each row/statement, and how big were the batches versions?

Murder Chicken

M

Murder Chicken•5/9/23, 12:23 AM

50k updates. Once I split it into 10k batch batches, it went through.

➜  npx wrangler@d1 d1 execute test-db --file 0000_initial.sql

🌀 Mapping SQL input into an array of statements
🌀 Parsing 25 statements
🌀 Executing on test-db (c020574a-5623-407b-be0c-cd192bab9545):

➜  npx wrangler@d1 d1 execute test-db --file 0000_initial.sql

🌀 Mapping SQL input into an array of statements
🌀 Parsing 25 statements
🌀 Executing on test-db (c020574a-5623-407b-be0c-cd192bab9545):

CREATE TRIGGER 'updated_records_to_changelog' AFTER UPDATE OF 'status' ON 'availabilities'
WHEN OLD.status <> NEW.status
BEGIN
  INSERT INTO changelog (c_id, for_date, status_was, status_is) 
  VALUES (OLD.c_id, OLD.for_date, OLD.status, NEW.status);
END;

CREATE TRIGGER 'updated_records_to_changelog' AFTER UPDATE OF 'status' ON 'availabilities'
WHEN OLD.status <> NEW.status
BEGIN
  INSERT INTO changelog (c_id, for_date, status_was, status_is) 
  VALUES (OLD.c_id, OLD.for_date, OLD.status, NEW.status);
END;

  (error) Error: Error: Error 9000: exception caught in D1 core. unreachable RuntimeError: unreachable
    at wasm://wasm/00f5753e:wasm-function[4783]:0x31be54
    at wasm://wasm/00f5753e:wasm-function[4836]:0x322be4
    at wasm://wasm/00f5753e:wasm-function[4877]:0x32c7d6
    at wasm://wasm/00f5753e:wasm-function[237]:0x29575
    at wasm://wasm/00f5753e:wasm-function[4973]:0x34351d
    at Object.s2 [as query] (index.js:2418:157)
    at async Sqlite.query (index.js:3205:23)
    at async sqliteQuery (index.js:9409:29)
    at async index.js:9167:22

  (error) Error: Error: Error 9000: exception caught in D1 core. unreachable RuntimeError: unreachable
    at wasm://wasm/00f5753e:wasm-function[4783]:0x31be54
    at wasm://wasm/00f5753e:wasm-function[4836]:0x322be4
    at wasm://wasm/00f5753e:wasm-function[4877]:0x32c7d6
    at wasm://wasm/00f5753e:wasm-function[237]:0x29575
    at wasm://wasm/00f5753e:wasm-function[4973]:0x34351d
    at Object.s2 [as query] (index.js:2418:157)
    at async Sqlite.query (index.js:3205:23)
    at async sqliteQuery (index.js:9409:29)
    at async index.js:9167:22