if it's returning a 7501 error most of the time you can safely retry

MMax (@rozenmd)if it's returning a 7501 error most of the time you can safely retry

micromashor•3/19/23, 9:13 PM

I was just using the dashboard interface to set up my tables, trying to INSERT INTO more than 2-3 values at a time causes a 500, and now whenever I load the list of tables I get 500 as well

micromashor•3/19/23, 9:15 PM

the weirdest behavior was the console showing internal error but the operation succeeded

Mmicromashor I was just using the dashboard interface to set up my tables, trying to INSERT I...

Max (@rozenmd)OP•3/19/23, 9:15 PM

the console tab? can you DM me what you were trying to run, I'll try fix it tomorrow

MMax (@rozenmd)the console tab? can you DM me what you were trying to run, I'll try fix it tomo...

micromashor•3/19/23, 9:21 PM

ofc now I can't get it to reproduce the error I was getting in the console tab ...or the 500 error when trying to load the tables tab

micromashor•3/19/23, 9:21 PM

guess it's working then lol

Mmicromashor ofc now I can't get it to reproduce the error I was getting in the console tab ....

Max (@rozenmd)OP•3/19/23, 10:22 PM

yeah might be that bug where it's safe to retry

micromashor•3/19/23, 10:27 PM

ah... figured it out - was my own mistake because I primarily use MySQL. I tried to do the following, which works in MySQL but doesn't work with SQLite

CREATE TABLE my_table (my_field TEXT);
-- need to use double apostrophe instead of backslash escaping
INSERT INTO my_table VALUES ('body with escaped string can\'t be done');

CREATE TABLE my_table (my_field TEXT);
-- need to use double apostrophe instead of backslash escaping
INSERT INTO my_table VALUES ('body with escaped string can\'t be done');

micromashor•3/19/23, 10:28 PM

For whatever reason that produced a 500 error when I first tried it, but now it correctly returns the SQLite error

micromashor•3/19/23, 10:49 PM

I still get sporadic 500 errors when I try to load the tables tab, can't figure out why. I'll go ahead and send over the database info in case that's of any help

ZZiga Zajc Won't KV store always consume a lot less resources?

Hello, I’m Allie!•3/20/23, 7:30 AM

Generally yes, but many apps just don’t work very well on a KV model

ZZiga Zajc It would be really helpful if Cloudflare could at least provide us with initial ...

Epailes•3/20/23, 11:11 AM

I'm personally expecting it somewhere in between R2 and KV pricing wise, as D1 isn't distributed globally like KV is, and the processing cost will be covered by the worker executing the query, but I've no idea all the stuff they're doing behind the scenes for transnational requests etc which might drive it up.

Epailes•3/20/23, 11:15 AM

I hope it's close to R2 pricing wise, with replicated read replicas costs based on usage, and the compute costs being one of the higher parts but that's basically the worker executing the query.
Although I don't think it'll be like that, they'll likely need something funky behind the scenes to support D1 instances >100MB as that's more than a worker can store in memory, so perhaps it'll be simple pricing for small D1 instances and complex pricing for larger D1 instances? Who knows

Walshy•3/20/23, 11:22 AM

what do you mean?

Epailes•3/20/23, 11:28 AM

I'd interpreted that as they'll replicate it where/when there's sufficient demand, not that it'll be auto replicated like KV is

Epailes•3/20/23, 11:35 AM

I'd honestly prefer D1 not be replicated to every datacentre, or at least for that to be configurable, that'll really drive up the costs and make it unsuitable for some use cases that are more cost sensitive.

ZZiga Zajc I though D1 will also replicate like KV

Hello, I’m Allie!•3/20/23, 11:36 AM

KV doesn't replicate

Hello, I’m Allie!•3/20/23, 11:36 AM

Or at least not at that scale