hmm, can I have a duplicate name database though?

Farhian•9/19/23, 3:45 PM

I do not think so... what I did (which is probably NOT a good practice) was to do a backup first (you need it anyway for the migration), delete it (it did allow me to delete even if I had a worker using it) - like you I wanted to use the same name, went through the beta migration, updated the toml binding and used the new ID and then redployed the worker. In my case, it was OK to have an outage

Farhian•9/19/23, 3:52 PM

or the same one

KKev ```[mf:inf] POST / 200 OK (2598ms) workerd/jsg/jsg.c++:136: error: took recursiv...

Matt Silverlock•9/19/23, 4:52 PM

How are you getting these? Local mode? From a query to a remote D1 DB? (this is all open source code, but we shouldn't be emitting them)

Farhian•9/19/23, 4:52 PM

@.k.e.v. I have no idea - it was working last night and not working in the morning - we did not inject anything over night

Ddave hmm, can I have a duplicate name database though?

itsmatteomanf•9/19/23, 5:06 PM

Database are accessed by uuids, so yeah, I think DBs can have the same name.

itsmatteomanf•9/19/23, 5:07 PM

You can’t have two bindings of the same name, but if you replace you should be fine.

Farhian•9/19/23, 5:07 PM

I remember trying to create 2 DBs with the same name in the portal and it did not let me - maybe I remember it wrong?

itsmatteomanf•9/19/23, 5:07 PM

Oh, wait. I might be thinking like KV does…

Farhian•9/19/23, 5:09 PM

I just tried it

itsmatteomanf•9/19/23, 5:09 PM

Yeah, it’s names…

Farhian•9/19/23, 5:09 PM

MMatt Silverlock How are you getting these? Local mode? From a query to a remote D1 DB? (this is ...

Max (@rozenmd)•9/19/23, 5:16 PM

mf:infmf:inf is local

Max (@rozenmd)•9/19/23, 5:17 PM

looks like workerd stack traces

Iitsmatteomanf Database are accessed by uuids, so yeah, I think DBs can have the same name.

Max (@rozenmd)•9/19/23, 5:18 PM

nah we put a unique index on name for each account earlier in the year

Matt Silverlock•9/19/23, 5:29 PM

For clarity, @.k.e.v.'s report is entirely local - e.g. D1 running locally as part of local dev vs. the issue others are seeing.

Farhian•9/19/23, 8:40 PM

Any update on the database access problem? Thanks!

FFarhian Any update on the database access problem? Thanks!

Matt Silverlock•9/19/23, 9:47 PM

This is rolling out now. Your DB was last on the east coast and we're about 35% done there.

Farhian•9/19/23, 9:48 PM

ooo

Farhian•9/19/23, 9:48 PM

thanks!

KKev FWIW my production D1 is back up 🙂

Matt Silverlock•9/19/23, 9:59 PM

Yep, I see that just now: "2023-09-19T21:51:02.570Z""2023-09-19T21:51:02.570Z" for last touched

KKev I might have celebrated a bit too early

Matt Silverlock•9/19/23, 10:00 PM

Yeah - still ~35% rolled out. Luck of the draw.

Farhian•9/19/23, 10:03 PM

I hope mine will be fixed before @.k.e.v. 's

Farhian•9/19/23, 10:31 PM

Mine is now working

Farhian•9/19/23, 10:32 PM

(much slower than usual but working

)

Farhian•9/19/23, 10:34 PM

I spoke to soon. I can see the DB, but when I try to query a row: {
"result": [],
"success": false,
"errors": [
{
"code": 7500,
"message": "internal error"
}
],
"messages": []
}

Farhian•9/19/23, 10:36 PM

It worked after a few refreshes - maybe it is due to the fix process still being rolled out