I’d avoid doing that. D1 is still alpha so not good for production

CCyb3r-Jak3 I’d avoid doing that. D1 is still alpha so not good for production

R

Rabid•8/3/23, 1:43 PM

Well my app isn't "production" ready either, just more of a public preview (test) right now for early adopters

N

nejc•8/3/23, 2:12 PM

Hi all, I am getting a fetch problem that was mentioned above as well. Code is generated with wrangler and the interesting thing is that INSERT works (with .run()), but when I do SELECT (with .all()) I get fetch error

N

nejc•8/3/23, 2:12 PM

TypeError: Cannot read properties of undefined (reading 'fetch')\n    at No._send (worker.js:34:466)\n    at Za.all (worker.js:34:1936)\n    at pu (worker.js:33:63946)\n    at async Object.fetch (worker.js:33:63296)

TypeError: Cannot read properties of undefined (reading 'fetch')\n    at No._send (worker.js:34:466)\n    at Za.all (worker.js:34:1936)\n    at pu (worker.js:33:63946)\n    at async Object.fetch (worker.js:33:63296)

TypeError: Cannot read properties of undefined (reading 'fetch')\n    at No._send (worker.js:34:466)\n    at Za.all (worker.js:34:1936)\n    at pu (worker.js:33:63946)\n    at async Object.fetch (worker.js:33:63296)

TypeError: Cannot read properties of undefined (reading 'fetch')\n    at No._send (worker.js:34:466)\n    at Za.all (worker.js:34:1936)\n    at pu (worker.js:33:63946)\n    at async Object.fetch (worker.js:33:63296)

N

nejc•8/3/23, 2:13 PM

this was all working correctly until last couple of days

N

nejc•8/3/23, 2:13 PM

I tried this on old alpha DB and also tried creating a new DB

N

nejc•8/3/23, 2:13 PM

both are returning the same error

Nnejc Hi all, I am getting a fetch problem that was mentioned above as well. Code is g...

M

Matt Silverlock•8/3/23, 2:22 PM

Can you please share a code snippet, and which version of

wrangler

wrangler

is being used here?

Nnick The code downloaded from another computer again, why does the part that binds D1...

M

Matt Silverlock•8/3/23, 2:24 PM

This is part of the alpha. We don't directly support going back and forth between wrangler and the dashboard just yet. Once we move the D1 binding out of wrangler (very soon), this will be fixed. Hold tight!

MMatt Silverlock Can you please share a code snippet, and which version of `wrangler` is being us...

N

nejc•8/3/23, 2:25 PM

I am using wrangler 3.4.0 to generate code

N

nejc•8/3/23, 2:26 PM

this is select that I am doing

N

nejc•8/3/23, 2:27 PM

await env.DB
    .prepare(
      'SELECT error, provider, created_at FROM errors WHERE created_at >=?1'
    )
    .bind(timestamp)
    .all()

await env.DB
    .prepare(
      'SELECT error, provider, created_at FROM errors WHERE created_at >=?1'
    )
    .bind(timestamp)
    .all()

await env.DB
    .prepare(
      'SELECT error, provider, created_at FROM errors WHERE created_at >=?1'
    )
    .bind(timestamp)
    .all()

await env.DB
    .prepare(
      'SELECT error, provider, created_at FROM errors WHERE created_at >=?1'
    )
    .bind(timestamp)
    .all()

N

nejc•8/3/23, 2:29 PM

where insert is working just fine

N

nejc•8/3/23, 2:29 PM

only select is returning fetch error

Nnejc I am using wrangler 3.4.0 to generate code

J

Jsx•8/3/23, 2:57 PM

their is no target provided for bind

env.DB
    .prepare(
      'SELECT error, provider, created_at FROM errors WHERE created_at = ?'
    )
    .bind(timestamp)
    .all()

env.DB
    .prepare(
      'SELECT error, provider, created_at FROM errors WHERE created_at = ?'
    )
    .bind(timestamp)
    .all()

env.DB
    .prepare(
      'SELECT error, provider, created_at FROM errors WHERE created_at = ?'
    )
    .bind(timestamp)
    .all()

env.DB
    .prepare(
      'SELECT error, provider, created_at FROM errors WHERE created_at = ?'
    )
    .bind(timestamp)
    .all()

Did you mean to do this? I am sorry if I got it wrong.

N

nejc•8/3/23, 3:00 PM

@heyjsx sorry for that, didn't copy the whole thing. You are right

N

nejc•8/3/23, 3:01 PM

updated snippet

J

Jsx•8/3/23, 3:03 PM

what's with the 1 at the last?

N

nejc•8/3/23, 3:15 PM

I am just using this to mark positions

O

oncetalk•8/3/23, 4:36 PM

I also encountered this situation yesterday, and repeated testing found that it was a problem with d1. Now, I have solved the problem by recreating the database and recreating the worker, then rebinding and importing the old database into the new database. However, my website has been greatly affected: (Remember, don't edit the code online now, once you do this, you will make an error)

MMatt Silverlock This is part of the alpha. We don't directly support going back and forth betwee...

O

oncetalk•8/3/23, 4:38 PM

thank you

MMatt Silverlock This is part of the alpha. We don't directly support going back and forth betwee...

O

oncetalk•8/3/23, 4:41 PM

And then, move the D1 binding out of wrangler? Does this mean that the d1 database can be bound on the dashboard?

Ooncetalk And then, move the D1 binding out of wrangler? Does this mean that the d1 databa...

M

Matt Silverlock•8/3/23, 4:42 PM

That is the plan.

MMatt Silverlock That is the plan.

O

oncetalk•8/3/23, 4:42 PM

This is great, I'm looking forward to it!

C

chientrm.com•8/3/23, 5:01 PM

I completely move from PlanetScale to D1, have stronk faith

LLogan Grasby this is the way

C

chientrm.com•8/3/23, 5:03 PM

this is the way.

LLogan Grasby Is --experimental-backend the new default?

U

Unsmart•8/3/23, 5:04 PM

it should be yes

C

chientrm.com•8/3/23, 5:29 PM

select * from Audio where createdAt < '2023-03-23T11:16:31.500';

select * from Audio where createdAt < '2023-03-23T11:16:31.500';

select * from Audio where createdAt < '2023-03-23T11:16:31.500';

select * from Audio where createdAt < '2023-03-23T11:16:31.500';

C

chientrm.com•8/3/23, 5:30 PM

return

id=47,createdAt='2023-03-23T11:16:31.500'

id=47,createdAt='2023-03-23T11:16:31.500'

id=47,createdAt='2023-03-23T11:16:31.500'

id=47,createdAt='2023-03-23T11:16:31.500'

C

chientrm.com•8/3/23, 5:30 PM

smth wrong with D1 date comparision

LLogan Grasby Is --experimental-backend the new default?

M

Matt Silverlock•8/3/23, 5:43 PM

https://developers.cloudflare.com/d1/changelog/#new-default-storage-subsystem

Changelog · Cloudflare D1 docs

Databases using D1’s new storage subsystem can now grow to 500 MB each, up from the previous 100 MB limit. This applies to both existing and newly …

Original message was deleted

N

nejc•8/3/23, 6:33 PM

With removing wrapper, you are also removing

__D1_BETA__

__D1_BETA__

__D1_BETA__

__D1_BETA__ from D1 binding prefix? Does this means that you will also have UI in dashboard as part of this wrangler release

N

nejc•8/3/23, 6:37 PM

I tried doing build based on this PR https://github.com/cloudflare/workers-sdk/pull/3595, but I am getting DB not found

N

nejc•8/3/23, 6:42 PM

@skye_31 so in this release you will just remove shim from wrangler?

N

nejc•8/3/23, 6:46 PM

great, do you maybe know when this wrangler release is going out?

N

nejc•8/3/23, 6:53 PM

thank you

Eetrepum Is there a straightforward way to download a dump of a new storage engine d1 dat...

M

Matt Silverlock•8/3/23, 8:06 PM

There is not.

MMatt Silverlock There is not.

A

Adi•8/4/23, 1:47 AM

Out of curiosity, is this on the roadmap?

AAdi Out of curiosity, is this on the roadmap?

M

Matt Silverlock•8/4/23, 1:55 AM

Further out. We’re focused on expanding Time Travel and many other core things (performance, larger DBs, more analytics, etc) - we think Time Travel is more valuable for most folks.

MMatt Silverlock Further out. We’re focused on expanding Time Travel and many other core things (...

A

Adi•8/4/23, 1:59 AM

That's quite fair. I mostly agree that those features would be much more useful.

Maybe an explanation of how CF protects against catastrophic failure in the backend would be beneficial until then.
I'm mostly thinking from the perspective of someone who wants to use D1 in production, some understanding on how likely/unlikely data loss is would be very helpful.

N

nick•8/4/23, 2:03 AM

After editing the worker code online, D1 still encounters errors. Downloading it to the local location using Wrangler and redeploying it will also cause errors. Can we restore normal operations today? thanks

Ggeelen I'm looking forward to making that possible: branching a new DB for testing/deve...

A

Adi•8/4/23, 2:07 AM

Honestly so keen for this

. The stuff you guys are doing with D1 is really exciting! We basically have our entire stack on Cloudflare, so we're waiting eagerly for more D1 goodness XD

Ggeelen that doesn't directly answer your data loss question, but it's the sort of flexi...

A

Adi•8/4/23, 2:09 AM

All good. Thanks for providing insight

. It's simply enough to write a snapshot cron with current DB sizes. It would only become unsustainable once DB sizes get a lot larger

I’d avoid doing that. D1 is still alpha so not good for production

Similar Threads

Similar Threads

Similar Threads