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

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.

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

Sure - I'm not saying there's any reason the ones you listed shouldn't be allowed, I don't represent the Workers team. They just haven't currently allowed them, so that's why you get that error.

Original message was deleted

Lucian•7/20/23, 1:12 AM

I think it is the dashboard. I had a similar issue with a CURRENT_TIMESTAMP DEFAULT value. When in code worked fine (the proper date was inserted) but when adding records in dashboard I got the text 'CURRENT_TIMESTAMP '

micromashor•7/20/23, 6:31 AM

Bug report: the dashboard table viewer munches tables which have generated columns
to reproduce:

CREATE TABLE example (
    fruit TEXT,
    fruit_but_lowercase TEXT GENERATED ALWAYS AS (lower(fruit)) VIRTUAL,
    vegetable TEXT
);

INSERT INTO example (fruit, vegetable) VALUES
    ('Apples', 'Carrots'),
    ('Bananas', 'Broccoli');

CREATE TABLE example (
    fruit TEXT,
    fruit_but_lowercase TEXT GENERATED ALWAYS AS (lower(fruit)) VIRTUAL,
    vegetable TEXT
);

INSERT INTO example (fruit, vegetable) VALUES
    ('Apples', 'Carrots'),
    ('Bananas', 'Broccoli');

micromashor•7/20/23, 6:32 AM

if you run

SELECT * FROM example

SELECT * FROM example

with wrangler or the dashboard console, it works as expected, but the table viewer shows this:

micromashor•7/20/23, 6:39 AM

99% sure this is happening because the dashboard appears to use the

table_info

table_info

pragma to discover the structure of the table, when, for historical reasons, that pragma doesn't show generated columns -

table_xinfo

table_xinfo

must be used instead. (see https://www.sqlite.org/gencol.html 2.3 #9)

LLucian I think it is the dashboard. I had a similar issue with a CURRENT_TIMESTAMP DEFA...

Max (@rozenmd)•7/20/23, 10:08 AM

yeah, dashboard bug - default values render weirdly

Mmicromashor 99% sure this is happening because the dashboard appears to use the `table_info`...

Max (@rozenmd)•7/20/23, 10:10 AM

cheers for the bug report + the fix MeowHeartCloudflare

micromashor•7/20/23, 4:42 PM

I'm having trouble getting foreign key constraints to work. I know with SQLite you need to run

PRAGMA foreign_keys=on

PRAGMA foreign_keys=on

on every connection, but this seems to always be a no-op. Anyone else run into this before?

Mmicromashor I'm having trouble getting foreign key constraints to work. I know with SQLite y...

Lucian•7/20/23, 5:31 PM

They worked for me. What makes you think they didn't work for you and how were they created? I think in sqlite you can only create them within CREATE TABLE and not with ALTER TABLE ADD CONSTRAINT .

LLucian They worked for me. What makes you think they didn't work for you and how were t...

micromashor•7/20/23, 5:38 PM

Yes, all of them were created within the CREATE TABLE statements. But the DB happily accepts garbage data which should be caught by foreign key constraints. Like I said, I couldn't even get the pragma turned on to begin with.

Mmicromashor Yes, all of them were created within the CREATE TABLE statements. But the DB hap...

Lucian•7/20/23, 5:58 PM

Hmm, to be precise the foreign key constraints screamed at me when trying to drop and recreate a table (referenced by ) but I never really tried to add data violating the constraints. So my anecdotal example might not be relevant to you

LLucian Hmm, to be precise the foreign key constraints screamed at me when trying to dro...

micromashor•7/20/23, 6:14 PM

Were you using the alpha backend? One difference I just found is that for some reason, the alpha backend defaults to

foreign_keys=1

foreign_keys=1

, while the beta backend defaults to

foreign_keys=0

foreign_keys=0

CREATE TABLE example ( fruit TEXT, fruit_but_lowercase TEXT GENERATED ALWAYS AS (lower(fruit)) VIRTUAL, vegetable TEXT ); INSERT INTO example (fruit, vegetable) VALUES ('Apples', 'Carrots'), ('Bananas', 'Broccoli');

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

Similar Threads