Many thanks, seems like a very clear pricing model. Do you have a sense of how likely it will be you

Ffork Many thanks, seems like a very clear pricing model. Do you have a sense of how l...

M

can't say/don't know tbh, but we're aiming to be affordable w/ very clear pricing, so would iterate towards that goal if we did change

F

forkOP•8/22/23, 10:46 AM

(You might want to update either this blog post "D1: We turned it up to 11" or the pricing page header as it seems to suggest the blog post has the more up-to-date information)

Ffork (You might want to update either this blog post "D1: We turned it up to 11" or t...

M

Max (@rozenmd)•8/22/23, 10:49 AM

fair point, will do

N

Nat•8/22/23, 1:22 PM

I'm trying to use d1 in my worker but something about adding the wrangler config totally broke my

wrangler dev

wrangler dev

:

⎔ Starting local server...
workerd/server/workerd-api.c++:615: error: wrapped binding module can't be resolved (internal modules only); moduleName = cloudflare-internal:d1-api
workerd/util/symbolizer.c++:99: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use `--test_env=LLVM_SYMBOLIZER=<path>`.
workerd/jsg/util.c++:275: error: e = workerd/server/workerd-api.c++:635: failed: expected !value.IsEmpty(); global did not produce v8::Value
stack: 104c8d3cf 104f000cf 104c55d6f 104c5ad4f 104c5d717 104c5c397 104c4fe87 104c4fc23 104c4fa8f 104c4fa77 106562367 1065625c3 106560d1b 106560aeb 104c441ab 1a8577f27; sentryErrorContext = jsgInternalError
service core:user:<MY_PROJECT_NAME>: Uncaught Error: internal error
✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

⎔ Starting local server...
workerd/server/workerd-api.c++:615: error: wrapped binding module can't be resolved (internal modules only); moduleName = cloudflare-internal:d1-api
workerd/util/symbolizer.c++:99: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use `--test_env=LLVM_SYMBOLIZER=<path>`.
workerd/jsg/util.c++:275: error: e = workerd/server/workerd-api.c++:635: failed: expected !value.IsEmpty(); global did not produce v8::Value
stack: 104c8d3cf 104f000cf 104c55d6f 104c5ad4f 104c5d717 104c5c397 104c4fe87 104c4fc23 104c4fa8f 104c4fa77 106562367 1065625c3 106560d1b 106560aeb 104c441ab 1a8577f27; sentryErrorContext = jsgInternalError
service core:user:<MY_PROJECT_NAME>: Uncaught Error: internal error
✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

⎔ Starting local server...
workerd/server/workerd-api.c++:615: error: wrapped binding module can't be resolved (internal modules only); moduleName = cloudflare-internal:d1-api
workerd/util/symbolizer.c++:99: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use `--test_env=LLVM_SYMBOLIZER=<path>`.
workerd/jsg/util.c++:275: error: e = workerd/server/workerd-api.c++:635: failed: expected !value.IsEmpty(); global did not produce v8::Value
stack: 104c8d3cf 104f000cf 104c55d6f 104c5ad4f 104c5d717 104c5c397 104c4fe87 104c4fc23 104c4fa8f 104c4fa77 106562367 1065625c3 106560d1b 106560aeb 104c441ab 1a8577f27; sentryErrorContext = jsgInternalError
service core:user:<MY_PROJECT_NAME>: Uncaught Error: internal error
✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

⎔ Starting local server...
workerd/server/workerd-api.c++:615: error: wrapped binding module can't be resolved (internal modules only); moduleName = cloudflare-internal:d1-api
workerd/util/symbolizer.c++:99: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use `--test_env=LLVM_SYMBOLIZER=<path>`.
workerd/jsg/util.c++:275: error: e = workerd/server/workerd-api.c++:635: failed: expected !value.IsEmpty(); global did not produce v8::Value
stack: 104c8d3cf 104f000cf 104c55d6f 104c5ad4f 104c5d717 104c5c397 104c4fe87 104c4fc23 104c4fa8f 104c4fa77 106562367 1065625c3 106560d1b 106560aeb 104c441ab 1a8577f27; sentryErrorContext = jsgInternalError
service core:user:<MY_PROJECT_NAME>: Uncaught Error: internal error
✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

The wrangler.toml config seems pretty straightforward:

[[d1_databases]]
  binding = "DB" # i.e. available in your Worker on env.DB
  database_name = "REDACTED"
  database_id = "REDACTED"

[[d1_databases]]
  binding = "DB" # i.e. available in your Worker on env.DB
  database_name = "REDACTED"
  database_id = "REDACTED"

[[d1_databases]]
  binding = "DB" # i.e. available in your Worker on env.DB
  database_name = "REDACTED"
  database_id = "REDACTED"

[[d1_databases]]
  binding = "DB" # i.e. available in your Worker on env.DB
  database_name = "REDACTED"
  database_id = "REDACTED"

Could someone help me sort this out?

N

Nat•8/22/23, 1:36 PM

Looks like ^ happens when you try to add a d1 config to your

wrangler.toml

wrangler.toml

but you're still using the old ServiceWorker format.

wrangler deploy

wrangler deploy

gave a much better error message that helped me sort this out. But maybe y'all can improve that error message on

wrangler dev

wrangler dev

MMatt Silverlock There is no support for downloading backups at this point. You don’t need to wit...

C

Cretezy•8/22/23, 2:05 PM

I think it's very important to be able to export data out of 3rd parties. I strongly believe backups/exports should be implemented

CCretezy I think it's _very_ important to be able to export data out of 3rd parties. I st...

H

Hello, I’m Allie!•8/22/23, 2:07 PM

Note too that afaik this is a planned feature at some point, it just isn’t built yet.

C

Cretezy•8/22/23, 2:07 PM

Thanks, that makes sense.

C

Cretezy•8/23/23, 4:17 AM

When will D1 be accessible through the Cloudflare API?
What would be the best way to manually implement exporting/backup?

C

Cretezy•8/23/23, 4:29 AM

Is appears probably using dump and a custom endpoint? https://developers.cloudflare.com/d1/platform/client-api/#await-dbdump

D1 client API · Cloudflare D1 docs

As part of our Client API, both static and prepared statements are supported. Best practice is to use prepared statements which are precompiled …

CCretezy When will D1 be accessible through the Cloudflare API? What would be the best wa...

C

chientrm.com•8/23/23, 4:30 AM

you can use this package to access D1 from outside: https://github.com/chientrm/wrangler-proxy

TTom Hi there ! I've made a url shortening service using workers & a D1 database. I...

M

Max (@rozenmd)•8/23/23, 3:26 PM

you could create a user-land backup using a script like d1-database

M

Max (@rozenmd)•8/23/23, 3:29 PM

otherwise, you can time travel via the D1 console in Cloudflare's dashboard:

TTom Hi there ! I've made a url shortening service using workers & a D1 database. I...

D

Dahoom•8/23/23, 10:40 PM

I recommend using this repo by Nora soderlund, it's amazing and I'm using it myself https://github.com/nora-soderlund/cloudflare-d1-backups

GitHub

GitHub - nora-soderlund/cloudflare-d1-backups: A package to dump a ...

A package to dump a copy of your experimental D1 database through a worker. - GitHub - nora-soderlund/cloudflare-d1-backups: A package to dump a copy of your experimental D1 database through a worker.

D

Dahoom•8/23/23, 10:44 PM

It saves the db as an sql file which can be set to a cron job and you can easily input the created file in wrangler and reset it as shown in the md of the repo

B

Ben-xD•8/24/23, 8:13 AM

I'm trying to run multiple migration/sql files on a D1 database. Is there a way I can have access to the D1 binding from inside a script (so I can read sql files and execute sql into D1)? Without being a "module worker" or "service worker"

M

Mikyari•8/24/23, 8:23 AM

Is procedure is available to use in D1 for now?

M

Mikyari•8/24/23, 8:23 AM

I did not see it in docs, but only this article: https://blog.cloudflare.com/whats-new-with-d1/

The Cloudflare Blog

D1: our quest to simplify databases

Get an inside look on the D1 experience today, what the team is currently working on and what’s coming up!

BBen-xD I'm trying to run multiple migration/sql files on a D1 database. Is there a way ...

A

advanced•8/24/23, 8:59 AM

you can try cfw-bindings-wrangler-bridge or the latest version of miniflare with getBindings api

BBen-xD I'm trying to run multiple migration/sql files on a D1 database. Is there a way ...

C

chientrm.com•8/24/23, 9:00 AM

https://github.com/chientrm/wrangler-proxy

Ssourabh.sashank Database Id: 08c3458c-812d-48bf-801d-5a87b4649f49 Not opening in dashboard, con...

M

Max (@rozenmd)•8/24/23, 9:09 AM

looks like an overloaded db using the old backend, would recommend the new backend

Ssourabh.sashank Can't we upgrade the same DB to be using new backend ?

M

Max (@rozenmd)•8/24/23, 10:35 AM

You'll need to export your database: https://developers.cloudflare.com/d1/learning/backups/#downloading-a-backup-locally
and import it into a new database running on the new backend: https://developers.cloudflare.com/d1/learning/importing-data/#import-an-existing-database

J

James•8/25/23, 1:06 AM

What does your worker look like? It has to be in modules format to use D1 from that error: https://developers.cloudflare.com/workers/learning/migrate-to-module-workers/

Migrate to ES modules format · Cloudflare Workers docs

This guide will show you how to migrate your Workers from the Service Worker format to the ES modules format.

SStar Bright I migrated it but now I'm getting ```js errors: [ { code: 10021, ...

M

Matt Silverlock•8/25/23, 7:08 AM

Make sure you’re uploading it as a module Worker.

SStar Bright I migrated it but now I'm getting ```js errors: [ { code: 10021, ...

M

Matt Silverlock•8/25/23, 7:09 AM

d1-database

C

chientrm.com•8/25/23, 12:31 PM

No.1 reason why I love D1?
Because I'm an SQL fetish.

R

rob•8/26/23, 12:19 AM

D1 bindings require module-format workers. [code: 10021]

R

rob•8/26/23, 12:19 AM

What do i need to do in my wrangler ?

Rrob What do i need to do in my wrangler ?

I

itsmatteomanf•8/26/23, 12:45 AM

Read the conversation just above

d1-database

R

rob•8/26/23, 1:04 AM

hey i fixed it! now im having an issue

R

rob•8/26/23, 1:05 AM

[[d1_databases]]
binding = "clickDB" # i.e. available in your Worker on env.clickDB
database_name = "click-db"
database_id = "XXXXXXXX"

[[d1_databases]]
binding = "clickDB" # i.e. available in your Worker on env.clickDB
database_name = "click-db"
database_id = "XXXXXXXX"

[[d1_databases]]
binding = "clickDB" # i.e. available in your Worker on env.clickDB
database_name = "click-db"
database_id = "XXXXXXXX"

[[d1_databases]]
binding = "clickDB" # i.e. available in your Worker on env.clickDB
database_name = "click-db"
database_id = "XXXXXXXX"

R

rob•8/26/23, 1:05 AM

I deploy and it says my worker has access to - D1 Databases:
- clickDB: click-db

R

rob•8/26/23, 1:05 AM

I get this error tho: TypeError: env.clickDB.put is not a function

Rrob I get this error tho: TypeError: env.clickDB.put is not a function

I

itsmatteomanf•8/26/23, 1:06 AM

Because it's not

I

itsmatteomanf•8/26/23, 1:06 AM

Read the docs.
https://developers.cloudflare.com/d1/platform/client-api/

D1 client API · Cloudflare D1 docs

As part of our Client API, both static and prepared statements are supported. Best practice is to use prepared statements which are precompiled …

R

rob•8/26/23, 1:06 AM

oo

Many thanks, seems like a very clear pricing model. Do you have a sense of how likely it will be you

Similar Threads

Similar Threads

Similar Threads