Hi! How to move out whole remote D1 to local D1? - Cloudflare Developers

© 2026 Hedgehog Software, LLC

More

Communities Docs About Terms Privacy

Xazu

XXazu Hi! How to move out whole remote D1 to local D1?

Max (@rozenmd)

M

Max (@rozenmd)•3/4/24, 11:22 AM

until we finish building it natively, https://github.com/nora-soderlund/cloudflare-d1-backups is likely the best option

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. - nora-soderlund/cloudflare-d1-backups

Xazu

X

XazuOP•3/4/24, 11:23 AM

Thank you!

D

DC•3/4/24, 3:41 PM

Hello eveyone. Does anyone know when D1 will be GA so that it can be used in production?

DDC Hello eveyone. Does anyone know when D1 will be GA so that it can be used in pr...

Epailes

E

Epailes•3/4/24, 4:42 PM

Planned for April

d1-database

d1-database

Ian

I

Ian•3/4/24, 10:47 PM

Do we have news of when dynamic bindings are available

Unsmart

U

Unsmart•3/4/24, 10:48 PM

Planned/hope to be by GA could be later

Ian

I

Ian•3/4/24, 11:48 PM

thanks, ill be waiting :Copium:

Junseong Park

J

Junseong Park•3/5/24, 2:21 AM

Is the value of

database_id

database_id

in the

wrangler.toml

wrangler.toml

file acceptable information to be made public?
If not, is there a way to hide this value from the Github repository? It looks like I can't use environment variables in this file.

James

J

James•3/5/24, 2:28 AM

Yes it’s fine. Anything you add in your wrangler.toml can be public

James

JJames Yes it’s fine. Anything you add in your wrangler.toml can be public

Junseong Park

J

Junseong Park•3/5/24, 2:30 AM

Thank you for good information!

Original message was deleted

Max (@rozenmd)

M

Max (@rozenmd)•3/5/24, 10:09 AM

did it throw an error or hang?

Lemon

L

Lemon•3/5/24, 1:20 PM

Hey guy I cannot find a solution to this error I'm facing.
I'm running D1 locally and I want to init my db and its throwing me this error, I tried deleting the node_modules as another dude said in this discord but it did nothing.
I tried different node versions too and rebuilding with the command but same thing happens...
Any idea?

Platform: Windows 11
Node: 16.13.0
App: Next.js with D1 and using the app router

testing-next-d1 on git main [!?] via nodejs v16.13.0 
> wrangler d1 execute --file ./init.sql pollo-4 --local
▲ [WARNING] Processing wrangler.toml configuration:

    - D1 Bindings are currently in alpha to allow the API to evolve before general availability.
      Please report any issues to https://github.com/cloudflare/workers-sdk/issues/new/choose
      Note: Run this command with the environment variable NO_D1_WARNING=true to hide this message

      For example: `export NO_D1_WARNING=true && wrangler <YOUR COMMAND HERE>`


--------------------
🚧 D1 is currently in open alpha and is not recommended for production data and traffic
🚧 Please report any bugs to https://github.com/cloudflare/workers-sdk/issues/new/choose
🚧 To request features, visit https://community.cloudflare.com/c/developers/d1
🚧 To give feedback, visit https://discord.gg/cloudflaredev
--------------------

🌀 Mapping SQL input into an array of statements

✘ [ERROR] The module '\\?\C:\Users\REDACTED\AppData\Roaming\npm\node_modules\wrangler\node_modules\better-sqlite3\build\Release\better_sqlite3.node'

  was compiled against a different Node.js version using
  NODE_MODULE_VERSION 111. This version of Node.js requires
  NODE_MODULE_VERSION 93. Please try re-compiling or re-installing
  the module (for instance, using `npm rebuild` or `npm install`).


If you think this is a bug then please create an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose

testing-next-d1 on git main [!?] via nodejs v16.13.0 
x

testing-next-d1 on git main [!?] via nodejs v16.13.0 
> wrangler d1 execute --file ./init.sql pollo-4 --local
▲ [WARNING] Processing wrangler.toml configuration:

    - D1 Bindings are currently in alpha to allow the API to evolve before general availability.
      Please report any issues to https://github.com/cloudflare/workers-sdk/issues/new/choose
      Note: Run this command with the environment variable NO_D1_WARNING=true to hide this message

      For example: `export NO_D1_WARNING=true && wrangler <YOUR COMMAND HERE>`


--------------------
🚧 D1 is currently in open alpha and is not recommended for production data and traffic
🚧 Please report any bugs to https://github.com/cloudflare/workers-sdk/issues/new/choose
🚧 To request features, visit https://community.cloudflare.com/c/developers/d1
🚧 To give feedback, visit https://discord.gg/cloudflaredev
--------------------

🌀 Mapping SQL input into an array of statements

✘ [ERROR] The module '\\?\C:\Users\REDACTED\AppData\Roaming\npm\node_modules\wrangler\node_modules\better-sqlite3\build\Release\better_sqlite3.node'

  was compiled against a different Node.js version using
  NODE_MODULE_VERSION 111. This version of Node.js requires
  NODE_MODULE_VERSION 93. Please try re-compiling or re-installing
  the module (for instance, using `npm rebuild` or `npm install`).


If you think this is a bug then please create an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose

testing-next-d1 on git main [!?] via nodejs v16.13.0 
x

Lemon

LLemon Hey guy I cannot find a solution to this error I'm facing. I'm running D1 locall...

Cyb3r-Jak3

C

Cyb3r-Jak3•3/5/24, 1:25 PM

What version of wrangler are you using? It looks extremely old.

Lemon

LLemon Hey guy I cannot find a solution to this error I'm facing. I'm running D1 locall...

Lemon

L

Lemon•3/5/24, 1:25 PM

If someone looking for a fix i got it ITS WEIRD
TLDR; Use pnpm....
When executing it with either wrangler ....wrangler .... or npm exec wrangler ...npm exec wrangler ... it throws the error above

Cyb3r-Jak3

CCyb3r-Jak3 What version of wrangler are you using? It looks extremely old.

Lemon

L

Lemon•3/5/24, 1:26 PM

its 3.28.4
not that old

Lemon

L

Lemon•3/5/24, 1:27 PM

its 10 days old...
i saw a video how to setup Next with D1 and the video is 11days old XD

Lemon

L

Lemon•3/5/24, 1:27 PM

anyways pnpm fixes that sqlite issue for some reason

Cyb3r-Jak3

C

Cyb3r-Jak3•3/5/24, 1:28 PM

Pretty sure that alpha warning has been removed for a while.

Lemon

L

Lemon•3/5/24, 1:28 PM

Cyb3r-Jak3

C

Cyb3r-Jak3•3/5/24, 1:32 PM

It looks like you might be using global installed wrangler and not specific to project.

Isaac McFadyen

I

Isaac McFadyen•3/5/24, 1:41 PM

~~It also looks like your Node version might be very old?~~ EDIT: see Leo's answer below.

Isaac McFadyen

I

Isaac McFadyen•3/5/24, 1:41 PM

That looks like a warning stating that you're using Node 11?

Isaac McFadyen

I

Isaac McFadyen•3/5/24, 1:42 PM

was compiled against a different Node.js version using NODE_MODULE_VERSION 111

Original message was deleted

Isaac McFadyen

I

Isaac McFadyen•3/5/24, 2:10 PM

Ah TY for the info then.

Lemon

LLemon Hey guy I cannot find a solution to this error I'm facing. I'm running D1 locall...

Max (@rozenmd)

M

Max (@rozenmd)•3/5/24, 3:23 PM

this log is from before wrangler v3

Epailes

EEpailes Planned for April https://discord.com/channels/595317990191398933/9920605818320...

D

DC•3/5/24, 5:09 PM

Thank you

Original message was deleted

V

Vy•3/5/24, 5:11 PM

We're working on export which will have a way to get just schema-only, which would output the current schema

SageSphinx63920

S

SageSphinx63920•3/5/24, 6:02 PM

Is it possible to set autoincrements for integer type values? Would be great

SageSphinx63920

S

SageSphinx63920•3/5/24, 6:03 PM

Or at least a work around for this if it is not implemented (yet)

Perksey

P

Perksey•3/5/24, 11:44 PM

noticed that there's a lot of "storage operation exceeding timeout" errors recently, in some cases this is resulting in customers losing paid entitlements for us

Perksey

P

Perksey•3/5/24, 11:44 PM

luckily we haven't launched yet and we're implementing a retry mechanism but does anyone know the cause of these?

Cyb3r-Jak3

C

Cyb3r-Jak3•3/5/24, 11:56 PM

What is your database ID? It helps the D1 debug quicker

TigersWay

T

TigersWay•3/6/24, 1:33 AM

Just published my personal "D1 backup" cli which so far allows "generated columns": https://github.com/TigersWay/d1-backup

GitHub

GitHub - TigersWay/d1-backup: Cloudflare D1 SQL backup downloader.

Cloudflare D1 SQL backup downloader. Contribute to TigersWay/d1-backup development by creating an account on GitHub.

wasauce

W

wasauce•3/6/24, 2:42 AM

Is there a way to read/write from D1 via Python from e.g. Google Cloud? I have some services already running there and if I start using D1 -- I would want to be able to connect from a worker on cloudflare but also from Google Cloud.

Sameer Ali

S

Sameer Ali•3/6/24, 3:00 AM

you can REST API https://developers.cloudflare.com/api/operations/cloudflare-d1-query-database

Cloudflare API Documentation

Interact with Cloudflare's products and services via the Cloudflare API

wasauce

W

wasauce•3/6/24, 3:08 AM

@Sameer Ali - thank you. I saw that - I think I am having double understanding -- is there a way to WRITE? It looks to me like one can QUERY and or create a new database but not write to a database. I am probably wrong and just not understanding the documentation.

Sameer Ali

S

Sameer Ali•3/6/24, 3:10 AM

REST API let you run any query including INSERT/UPDATE/SELECT

wasauce

W

wasauce•3/6/24, 3:10 AM

AH - my mistake. Thanks very much.

Vikash

V

Vikash•3/6/24, 11:12 AM

I see some time internal error in my logs, any suggestion where that's coming from?

Vikash

V

Vikash•3/6/24, 11:12 AM

D1_ERROR: internal error

D1_ERROR: internal error

Vikash

V

Vikash•3/6/24, 11:13 AM

Vikash

V

Vikash•3/6/24, 11:15 AM

This is my error reporter on a worker using hono -

app.onError(async (err, ctx) => {
  if (err instanceof HTTPException) {
    const msg = await err.res.text();
    return ctx.json({ message: msg }, err.status);
  } else {
    if (ctx.env.ENVIRONMENT != 'development') {
      const { url, method } = ctx.req.raw;
      let jsonBody = '';
      if (method == 'POST' || method == 'PUT') {
        jsonBody = await ctx.req.json();
      }
      await postToDiscord(
        err.message,
        JSON.stringify(
          {
            url: url,
            method: method,
            data: jsonBody,
          },
          null,
          2
        )
      );
    }
    return ctx.json({ message: 'Server error' }, 500);
  }
});

app.onError(async (err, ctx) => {
  if (err instanceof HTTPException) {
    const msg = await err.res.text();
    return ctx.json({ message: msg }, err.status);
  } else {
    if (ctx.env.ENVIRONMENT != 'development') {
      const { url, method } = ctx.req.raw;
      let jsonBody = '';
      if (method == 'POST' || method == 'PUT') {
        jsonBody = await ctx.req.json();
      }
      await postToDiscord(
        err.message,
        JSON.stringify(
          {
            url: url,
            method: method,
            data: jsonBody,
          },
          null,
          2
        )
      );
    }
    return ctx.json({ message: 'Server error' }, 500);
  }
});

Original message was deleted

Vikash

V

Vikash•3/6/24, 11:17 AM

Vikash

V

Vikash•3/6/24, 11:21 AM

Multiple queries, not shere which one throwing error but randomly once in a million -

Check if URL exits

SELECT id FROM Blocked WHERE url = ?

Then,

Insert into..............

cloudflareaccess.com

C

cloudflareaccess.com•3/6/24, 11:28 AM

@Sameer Ali @wasauce @Cyb3r-Jok3

cloudflareaccess.com

Ccloudflareaccess.com @Sameer Ali @wasauce @Cyb3r-Jok3

DaniFoldi

D

DaniFoldi•3/6/24, 11:35 AM

?pings

Flare

F

Flare•3/6/24, 11:35 AM

Please 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.

Jazz

J

Jazz•3/6/24, 3:27 PM

I'm developing a multiplayer game and I want to store data for my players. Players will hop around from server to server (like the game rust) but I want some persistent data such as player statistics, settings, etc. to exist outside the individual servers' data. I was wondering if D1 is a good option for something like this? I want my stack to scale automatically as we get more players, so I thought of D1. Also, it would be a single database for every player in the world. Is this is something D1 is good at or it really for meant for cloudflare pages/workers only

app.onError(async (err, ctx) => {
  if (err instanceof HTTPException) {
    const msg = await err.res.text();
    return ctx.json({ message: msg }, err.status);
  } else {
    if (ctx.env.ENVIRONMENT != 'development') {
      const { url, method } = ctx.req.raw;
      let jsonBody = '';
      if (method == 'POST' || method == 'PUT') {
        jsonBody = await ctx.req.json();
      }
      await postToDiscord(
        err.message,
        JSON.stringify(
          {
            url: url,
            method: method,
            data: jsonBody,
          },
          null,
          2
        )
      );
    }
    return ctx.json({ message: 'Server error' }, 500);
  }
});

app.onError(async (err, ctx) => {
  if (err instanceof HTTPException) {
    const msg = await err.res.text();
    return ctx.json({ message: msg }, err.status);
  } else {
    if (ctx.env.ENVIRONMENT != 'development') {
      const { url, method } = ctx.req.raw;
      let jsonBody = '';
      if (method == 'POST' || method == 'PUT') {
        jsonBody = await ctx.req.json();
      }
      await postToDiscord(
        err.message,
        JSON.stringify(
          {
            url: url,
            method: method,
            data: jsonBody,
          },
          null,
          2
        )
      );
    }
    return ctx.json({ message: 'Server error' }, 500);
  }
});

testing-next-d1 on git main [!?] via nodejs v16.13.0 
> wrangler d1 execute --file ./init.sql pollo-4 --local
▲ [WARNING] Processing wrangler.toml configuration:

    - D1 Bindings are currently in alpha to allow the API to evolve before general availability.
      Please report any issues to https://github.com/cloudflare/workers-sdk/issues/new/choose
      Note: Run this command with the environment variable NO_D1_WARNING=true to hide this message

      For example: `export NO_D1_WARNING=true && wrangler <YOUR COMMAND HERE>`


--------------------
🚧 D1 is currently in open alpha and is not recommended for production data and traffic
🚧 Please report any bugs to https://github.com/cloudflare/workers-sdk/issues/new/choose
🚧 To request features, visit https://community.cloudflare.com/c/developers/d1
🚧 To give feedback, visit https://discord.gg/cloudflaredev
--------------------

🌀 Mapping SQL input into an array of statements

✘ [ERROR] The module '\\?\C:\Users\REDACTED\AppData\Roaming\npm\node_modules\wrangler\node_modules\better-sqlite3\build\Release\better_sqlite3.node'

  was compiled against a different Node.js version using
  NODE_MODULE_VERSION 111. This version of Node.js requires
  NODE_MODULE_VERSION 93. Please try re-compiling or re-installing
  the module (for instance, using `npm rebuild` or `npm install`).


If you think this is a bug then please create an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose

testing-next-d1 on git main [!?] via nodejs v16.13.0 
x

testing-next-d1 on git main [!?] via nodejs v16.13.0 
> wrangler d1 execute --file ./init.sql pollo-4 --local
▲ [WARNING] Processing wrangler.toml configuration:

    - D1 Bindings are currently in alpha to allow the API to evolve before general availability.
      Please report any issues to https://github.com/cloudflare/workers-sdk/issues/new/choose
      Note: Run this command with the environment variable NO_D1_WARNING=true to hide this message

      For example: `export NO_D1_WARNING=true && wrangler <YOUR COMMAND HERE>`


--------------------
🚧 D1 is currently in open alpha and is not recommended for production data and traffic
🚧 Please report any bugs to https://github.com/cloudflare/workers-sdk/issues/new/choose
🚧 To request features, visit https://community.cloudflare.com/c/developers/d1
🚧 To give feedback, visit https://discord.gg/cloudflaredev
--------------------

🌀 Mapping SQL input into an array of statements

✘ [ERROR] The module '\\?\C:\Users\REDACTED\AppData\Roaming\npm\node_modules\wrangler\node_modules\better-sqlite3\build\Release\better_sqlite3.node'

  was compiled against a different Node.js version using
  NODE_MODULE_VERSION 111. This version of Node.js requires
  NODE_MODULE_VERSION 93. Please try re-compiling or re-installing
  the module (for instance, using `npm rebuild` or `npm install`).


If you think this is a bug then please create an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose

testing-next-d1 on git main [!?] via nodejs v16.13.0 
x