Running into an error today when trying to apply migrations. Was working fine for me yesterday so no

Running into an error today when trying to apply migrations. Was working fine for me yesterday so not sure whats going on.

[ERROR] A request to the Cloudflare API (/accounts/53b0f0b6a2f098df4d15b72741f23ba1/d1/database/0e8a4afd-b72b-4f12-99c2-1c7c9c9a74e5/backup) failed.

  The request is malformed: Experimental DBs do not support backups yet:
  0e8a4afd-b72b-4f12-99c2-1c7c9c9a74e5 (v3) [code: 7400]

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

[ERROR] A request to the Cloudflare API (/accounts/53b0f0b6a2f098df4d15b72741f23ba1/d1/database/0e8a4afd-b72b-4f12-99c2-1c7c9c9a74e5/backup) failed.

  The request is malformed: Experimental DBs do not support backups yet:
  0e8a4afd-b72b-4f12-99c2-1c7c9c9a74e5 (v3) [code: 7400]

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

[ERROR] A request to the Cloudflare API (/accounts/53b0f0b6a2f098df4d15b72741f23ba1/d1/database/0e8a4afd-b72b-4f12-99c2-1c7c9c9a74e5/backup) failed.

  The request is malformed: Experimental DBs do not support backups yet:
  0e8a4afd-b72b-4f12-99c2-1c7c9c9a74e5 (v3) [code: 7400]

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

[ERROR] A request to the Cloudflare API (/accounts/53b0f0b6a2f098df4d15b72741f23ba1/d1/database/0e8a4afd-b72b-4f12-99c2-1c7c9c9a74e5/backup) failed.

  The request is malformed: Experimental DBs do not support backups yet:
  0e8a4afd-b72b-4f12-99c2-1c7c9c9a74e5 (v3) [code: 7400]

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

yeehowOP•6/1/23, 7:04 PM

Yeah agreed

Yyeehow Running into an error today when trying to apply migrations. Was working fine fo...

Max (@rozenmd)•6/1/23, 7:22 PM

when you apply a migration for an experimental backend db, (for now) you need to pass --experimental-backend--experimental-backend

MMax (@rozenmd)when you apply a migration for an experimental backend db, (for now) you need to...

yeehowOP•6/1/23, 7:22 PM

ahhh ok thank you

Original message was deleted

Leon338•6/1/23, 9:21 PM

I'm not entirely sure but logically it has to scan every CompanyName or atleast the first digit, because even the last row could be this CompanyName. Could be fixed by setting a Limit at the End for example to find only the first one. But yes an Index sorted by CompanyName should help alot. Basically would change from O(n) to O(log(n))

Leon338•6/1/23, 9:26 PM

And keep in Mind the Reads are Size based. If your CompanyNames has an average length of 8 chars it would take 500 scans for one Read Unit. But maybe the Where statement is optimized so that it doesnt even read the entire CompanyName

Original message was deleted

Leon338•6/1/23, 9:34 PM

Nevermind I think im wrong with the Index. The WHERE LIKE statement can be different and also search if something contains anything. I don't even think a Index would help there and it's always O(n)

Original message was deleted

Leon338•6/1/23, 10:10 PM

Not if you have a % at the start and at the end, thats always an entire Table Scan

Leon338•6/1/23, 10:16 PM

But you could try to use Contains instead of Like that should be faster and is more optimized I guess

Leon338•6/1/23, 10:20 PM

And if the Company Name contains multiple Words you can look into a Fulltext Index, but I mean this type of Queries will always scan alot of rows

UUnsmart As I have already said in the past the pricing difference entirely depends. If y...

Matt Silverlock•6/1/23, 11:51 PM

You could fully scan a 1GB table 100,000 times before you reach the included 25 billion reads. Read units might add up fast but we give you billions and charge 1/10th of a penny per million.

Unsmart•6/1/23, 11:52 PM

That is true, I dont know what the cost for each would be for a normal usage as an actual database was mostly pointing out that KV is meant for larger storage blobs where if possible to store on D1 wouldnt be suitable cost wise

Unsmart•6/1/23, 11:53 PM

Probably shouldve made that more clear to be fair

MMatt Silverlock You could fully scan a 1GB table 100,000 times before you reach the included 25 ...

Matt Silverlock•6/1/23, 11:53 PM

D1 should always be cheaper for SQL/queryable type workloads. If you’re treating it like a big KV store with > 1MB rows then yeah, it’s not a good fit. That’s OK - that’s what KV is built for.

UUnsmart That is true, I dont know what the cost for each would be for a normal usage as ...

Matt Silverlock•6/1/23, 11:53 PM

Entirely agree.

MMatt Silverlock D1 should always be cheaper for SQL/queryable type workloads. If you’re treating...

Leon338•6/2/23, 1:17 AM

My thought was, if I use D1 to store Session Tokens (sorted) it would be 100x cheaper then KV. Even tho KV is basically the perfect fit for it.

LeftSpace•6/2/23, 11:43 AM

does d1 works on miniflare (local version)

LLeftSpace does d1 works on miniflare (local version)

Max (@rozenmd)•6/2/23, 11:47 AM

yep

LeftSpace•6/2/23, 11:56 AM

couldn't find on documentation. do i have to configure with wrangler.toml?

LLeftSpace couldn't find on documentation. do i have to configure with wrangler.toml?

Max (@rozenmd)•6/2/23, 11:57 AM

are you on wrangler 2 or 3?

LeftSpace•6/2/23, 11:58 AM

3.0.1

LeftSpace•6/2/23, 11:59 AM

A local session does not have access to your production data by default. To access your production (remote) database

LeftSpace•6/2/23, 11:59 AM

i see

Max (@rozenmd)•6/2/23, 11:59 AM

if you run

wrangler dev

wrangler dev

, it'll be accessing a local miniflare d1 instance

LeftSpace•6/2/23, 11:59 AM

so if i pass --remote

LeftSpace•6/2/23, 11:59 AM

it'll use remote db

Max (@rozenmd)•6/2/23, 11:59 AM

should be, yeah

LeftSpace•6/2/23, 12:00 PM

thanks >.<

LeftSpace•6/2/23, 12:01 PM

Any changes you make when running in --remote mode cannot be undone.

LeftSpace•6/2/23, 12:02 PM

so this will effect my already running remote code?

LeftSpace•6/2/23, 12:02 PM

i dont want that if thats the case.

LLeftSpace Any changes you make when running in --remote mode cannot be undone.

Hello, I’m Allie!•6/2/23, 12:04 PM

No, it’s more that if you accidentally break your database by using some buggy code locally, then you can’t just rollback when you stop the dev session. It doesn’t affect your deployed code, and once the D1 backup restore thing, then you can roll it back manually

LeftSpace•6/2/23, 12:05 PM

ah thats fair. yeah i'll just read data wont create any table n stuff Im good then.