Hi Matt, yes I am using the original backend since it has back-ups enabled. Is there a migration pat

Hi Matt, yes I am using the original backend since it has back-ups enabled. Is there a migration path planned from the original backend to the experimental backend when backups become available on the experimental as well?

《

《 Sarge 》•7/17/23, 8:30 PM

@Matt Anyway I'll leave this and come back to it tomorrow. Thanks for the help so far. I'll prob come back tomorrow with a solution hopefully. Thanks again

LLucian Hi Matt, yes I am using the original backend since it has back-ups enabled. Is t...

Matt Silverlock•7/17/23, 8:35 PM

Not an automated path in the near term (primarily because these are alpha databases, not production databases). You can easily export and then run execute DB_NAME --file=export.sqlexecute DB_NAME --file=export.sql to import your old database.

《《 Sarge 》So with that train of thought. I removed DBeaver from the process. I delete the ...

Matt Silverlock•7/17/23, 8:36 PM

I'd suggest opening an issue on GitHub — I think we have exhausted debugging here via Discord without seeing your SQL. I really suspect your migration/seed scripts are just not creating the right tables first.

MMatt Silverlock Not an automated path in the near term (primarily because these are alpha databa...

LucianOP•7/17/23, 9:27 PM

This will sound really dumb but, how do I export my database using Wrangler?

Original message was deleted

LucianOP•7/18/23, 12:38 AM

Thanks nora!
Just FYI, in case someone else runs into a problem that I ran into during the process:

On windows, after converting the backup to a sql file using sqlite3 (using sqlite3 <path-to-downloaded-file> .dump > latest.sql) when attempting to import via npx wrangler d1 execute <name> --file=latest.sql, wrangler was complaining about an imaginary synthax error like this:

near "��P": syntax error [code: 7500]".

It turns out this is an encoding problem, the sql file ended up encoded in UTF-8-BOM and had to be converted to UTF-8. You can do this using Notepad++ via the Encoding menu option and then saving. After which, the import worked flawlessly (18MB database imported in about 30 seconds or so)

MMatt Silverlock Not an automated path in the near term (primarily because these are alpha databa...

LucianOP•7/18/23, 1:37 AM

Is there a rough estimate regarding enabling backups on the experimental backend?
This backend is significantly faster, event without indexes, but I am reluctant to using it until I have backups running.

LLucian Is there a rough estimate regarding enabling backups on the experimental backend...

Cyb3r-Jak3•7/18/23, 1:47 AM

You can try it: d1-database

CCyb3r-Jak3 You can try it: https://discord.com/channels/595317990191398933/9920605818320323...

LucianOP•7/18/23, 2:34 AM

Thanks @Cyb3r-Jok3 Time travel seems super cool, but so far when following the blog post and trying stuff out (like this wrangler d1 time-travel info YOUR_DATABASE) I get [ERROR] Unknown argument: time-travel. I am using wrangler 3.2.0

LLucian Thanks @Cyb3r-Jok3 Time travel seems super cool, but so far when following the b...

Cyb3r-Jak3•7/18/23, 2:38 AM

I believe you need to be using the

d1

d1

release of the wrangler branch as it hasn't been merged into a release yet. If you do

npx wrangler@d1 d1 time-travel info <db>

npx wrangler@d1 d1 time-travel info <db>

then I believe it should work

CCyb3r-Jak3 I believe you need to be using the `d1` release of the wrangler branch as it has...

LucianOP•7/18/23, 2:41 AM

Just tried, it seems to not be working as of now . Unless I am doing something really wrong

npx wrangler@d1 d1 time-travel info <db>
X [ERROR] Unknown arguments: time-travel, info

lll-QWQ•7/18/23, 3:49 AM

Does D1 database have limit on how many tables you can create?

LLucian Just tried, it seems to not be working as of now . Unless I am doing something r...

Matt Silverlock•7/18/23, 3:58 AM

Double check you have the latest

wrangler@d1

wrangler@d1

branch. It definitely works. I am using the same public version as everyone else. But also note that this isn’t final - I’d suggest holding off until we officially release it if you rely on your database.

LLucian Thanks @Cyb3r-Jok3 Time travel seems super cool, but so far when following the b...

Matt Silverlock•7/18/23, 3:59 AM

Also, I spell out the commands in that comment, so please read it carefully

d1-database

Etrain•7/18/23, 12:49 PM

Hello, I've been digging through chat and the documentation to look for a way to use D1 with

vite dev

vite dev

and the best I could find is re-running the production build. https://discord.com/channels/595317990191398933/1042974692186804295/1048148731670835290

For SvelteKit specifically, it looks like the

platform

platform

parameter needs to be able to receive the D1 client library when developing locally: https://github.com/sveltejs/kit/issues/4292
That may eventually be addressable through the adapter. This would be great to have to improve the developer experience.
Could I be missing something meanwhile? The docs mention a

--d1

--d1

flag to set up the database binding locally, but I assume that's for the

wrangler

wrangler

CLI and not Vite.

EEtrain Hello, I've been digging through chat and the documentation to look for a way to...

Matt Silverlock•7/18/23, 1:23 PM

If you don't inject the binding into the application - vite or not - you won't be able to access the local DB. The flag — the binding — is what allows your app to talk to D1. Think of it like a DB driver = without it, there's no way for your code to talk to the DB. In lieu of that, you can see that others are mocking the

platform

platform

object and the APIs they need.

chientrm.com•7/18/23, 1:33 PM

how do I drop a

DEFAULT

DEFAULT

constraint?

Oodin im getting "* * * * *" @ 7/18/2023, 4:07:12 PM - Exception Thrown X [ERROR] ...

Matt Silverlock•7/19/23, 6:57 AM

Known bug with

DROP COLUMN

DROP COLUMN

specifically: d1-database

Original message was deleted

Matt Silverlock•7/19/23, 6:58 AM

Known bug: d1-database (see the messages either side of this linked one)

cdslash•7/19/23, 11:27 AM

I have some workers routes defined in my

wrangler.toml

wrangler.toml

that work in production:

routes = [
    { pattern = "*/send", zone_id = "[id]" },
    { pattern = "*/login", zone_id = "[id]" },
    { pattern = "*/services", zone_id = "[id]" },
]

routes = [
    { pattern = "*/send", zone_id = "[id]" },
    { pattern = "*/login", zone_id = "[id]" },
    { pattern = "*/services", zone_id = "[id]" },
]

when I print the login url (using Hono via

c.req.url

c.req.url

) I correctly get

https://foo.com/login

https://foo.com/login

when it's deployed to Cloudflare.

Locally though, with

wrangler dev

wrangler dev

, I get

http://send/login

http://send/login

it seems to be using the first route as the hostname, which is bizarre. Is this is known issue?

Ccdslash I have some workers routes defined in my `wrangler.toml` that work in production...

Max (@rozenmd)•7/19/23, 11:40 AM

can you please report this in https://github.com/cloudflare/workers-sdk/issues ?

Original message was deleted

Max (@rozenmd)•7/19/23, 11:41 AM

this is now live

MMax (@rozenmd)can you please report this in https://github.com/cloudflare/workers-sdk/issues ?

cdslash•7/19/23, 11:53 AM

I've reported and added a little more information, specifically that commenting out the wildcard route definitions makes it work as expected locally, but those are required for production.

https://github.com/cloudflare/workers-sdk/issues/3635

GitHub

🐛 BUG: reported url differs between production and local · Issue #3...

Which Cloudflare product(s) does this pertain to? Wrangler core What version(s) of the tool(s) are you using? 3.3.0 What version of Node are you using? No response What operating system are you usi...

Ccdslash I've reported and added a little more information, specifically that commenting ...

Max (@rozenmd)•7/19/23, 11:54 AM

cheers - btw #wrangler might be a better place to ask folks if they've run into this issue

MMax (@rozenmd)cheers - btw #wrangler might be a better place to ask folks if they've run into ...

cdslash•7/19/23, 12:08 PM

Great, thanks for the tip

MMax (@rozenmd)cheers - btw #wrangler might be a better place to ask folks if they've run into ...

cdslash•7/19/23, 12:42 PM

Only just realised I posted this in the D1 channel - sorry! Must've hit the wrong tab when aiming for wrangler (immediately above it)

Original message was deleted

Max (@rozenmd)•7/19/23, 1:58 PM

nah the idea is to keep them around so you can setup the project from scratch

Max (@rozenmd)•7/19/23, 1:59 PM

d1 keeps track of what you're already applied, but if you made a new db you could apply all migrations from the start and have a working copy

Max (@rozenmd)•7/19/23, 1:59 PM

yep

TTraffy I my migrating my CMS to edge platform. I exported data from mongo and it turns ...

Cyb3r-Jak3•7/19/23, 2:54 PM

They announced in a blog post that paid plan will be getting 1GB max. Only ETA is soontm

Nnexx same question, D1 doesn't work with this ``` insert into oauth (UserID, IsCool) ...

Matt Silverlock•7/19/23, 3:49 PM

ON DUPLICATE KEY

ON DUPLICATE KEY

isn’t supported by D1’s query engine (SQLite) - use

UPSERT

UPSERT

INSERT OR IGNORE

INSERT OR IGNORE

instead: https://stackoverflow.com/a/4330694/556573

Stack Overflow

UPSERT *not* INSERT or REPLACE

http://en.wikipedia.org/wiki/Upsert
Insert Update stored proc on SQL Server
Is there some clever way to do this in SQLite that I have not thought of?
Basically I want to update three out of four co...

Ashley•7/19/23, 6:22 PM

Quick question: when applying migrations to production databases, what are the most common ones that cause (or is there a list) requests to be held while the migration applies? I know the backup is one, but for example, are

ALTER TABLE

ALTER TABLE

likely to also cause requests to be held while it applies?

Ashley•7/19/23, 6:22 PM

And presumably things like creating new tables and inserting data won't cause such problems

Ashley•7/19/23, 6:23 PM

And similarly to alter table, adding indexes would possibly be one?

TTraffy I want to migrate my data to d1. I exported my mongo collection with 37000 docum...

Cyb3r-Jak3•7/19/23, 6:48 PM

D1 maxes out at 100 MB

Chaika•7/19/23, 6:53 PM

I've hit that before, it's just wayy too much for wrangler to handle/split properly, and even if you get past it, my experience was trying to insert any mass amount of data (like 20-40 MB in my case, was large rows) to the new experimental backend would just fail with a d1 error. Hopefully will improve/make it easier to import lots of data eventually, but it's still alpha

kian•7/19/23, 9:43 PM

table_list

table_list

table_info

table_info

and

table_xinfo

table_xinfo

work

kian•7/19/23, 9:44 PM

No other pragmas are currently allowed, but if you have a valid use-case for any others then open an issue on https://github.com/cloudflare/workerd/issues/new/choose for it to be considered.

Hi Matt, yes I am using the original backend since it has back-ups enabled. Is there a migration pat

Similar Threads

Similar Threads

Similar Threads