cloudflare / cloudflare/developer-platform

Exporting and importing locally gives "no such table: main.User: SQLITE_ERROR"

Open
#9 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

awaiting-response:cloudflare blocked product:d1
Dominant language
No language data
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

### What versions & operating system are you using?

wrangler 4.16.1

### Please provide a link to a minimal reproduction

_No response_

### Describe the Bug

I follow this article how to export and import d1.
https://developers.cloudflare.com/d1/best-practices/import-export-data/#export-an-existing-d1-database

```
npx wrangler d1 export xyz --remote --output=./database.sql
```

I remove `rm -rf .wrangler`

and then running
```
npx wrangler@latest d1 execute xyz-staging --file=database.sql
```

The sql file looks correct, but it looks like the export is not doing it correct in order

Image

You can see that _userOrganizations depends on User which has not been created yet, and if I switch the order then I get another SQL error about another table which does not exist.

### Please provide any relevant error logs

[wrangler-2025-05-23_10-58-30_040.log](https://github.com/user-attachments/files/20409177/wrangler-2025-05-23_10-58-30_040.log)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the documented `wrangler d1 export` and `wrangler d1 execute --file` commands, then inspect the generated `database.sql` and the linked Wrangler log. Verify whether exported table statements are ordered safely for their dependencies, and consider the import complete when the SQL file executes successfully against the staging database.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql, sqlite
Domain
databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.