Sure but if you want zero downtime, you duplicate the DB, drop the table, and switch the "connection
Sure but if you want zero downtime, you duplicate the DB, drop the table, and switch the "connection" (binding)
ZYes, that is something we've considered, it's just more work
ZWe're already having to work around multiple other issues that we didn't expect lol
くHi. I encountered a consistent issue when editing a row in a D1 table via the dashboard. Attempting to edit the following string causes a 404 Bad Request:
data.txt51B
くI'm not exactly sure which character is triggering the error — it might be due to a special character or even an invisible whitespace — but the issue is 100% reproducible when trying to update a row containing this exact value.
TI'd love to hear more. What other issues did you unexpectedly encounter?
ZBulk import API causing the database to be unusable (which is documented to be fair), the D1 API having severe rate limits (worked around by using our own worker as a proxy for SQL commands), some issue internally with D1 causing huge latency after we replaced a bulk of the data within the database that the team fixed
ZWe are using D1 in a slightly abnormal way, as a lookup table basically, so you probably won't experience the same problems if you're using it as a more traditional database 
TThank you!
Gdoes that end up in the url of the edit page?
くYes, the issue happens when click "Update" on a row that contains that string the value ends up in the URL, and that's when the 400 error oCcurs.
So it seems like the string being placed in the URL is causing the problem.
So it seems like the string being placed in the URL is causing the problem.
Gits likely a character that can't be in a url, like the one used as a space character, the browser is interpreting it as a space etc and that causes the 404
Gcan't say which specific one is the issue but I'd say thats the issue IMO
Jout of curiosity, does anyone know how D1 accomplishes autoincrement given its distributed nature?
JIt doesn’t - d1 isn’t distributed today. Your db exists in a single region
Jah, so the
--location CLI param isn't so much the primary location as it is the only location.Jgood to know, thank you @James!
JCurrently yep. The team has talked a lot about read replicas though, so I wouldn’t be surprised if we see something there soon 
Jawesome, i'll save my question for then, ha.
Greally hoping for more d1 news given the outerbase stuff but not holding my breath
JThat would be pretty great, fingers crossed!
Onoway read replicas
Zit's happening
SAre there any issues with D1 currently?
SI'm pushing stuff but they don't show up on the API
L
LNext question, when does this come to DO-based SQLite storage?
LD1 is the customer zero of DOs 
So, once we see it's good enough with D1 and iron out some things, DOs will get some version of it too.
So, once we see it's good enough with D1 and iron out some things, DOs will get some version of it too.LI would encourage people to try this out, and please give us feedback. Tell us cases it broke for you, or didn't do what you expected. Note that it's "beta". We are aware of some specific issues and are fixed as we speak to be rolled out over the next few weeks, so do your own testing to see if fits your workloads too.
CIMO at least for me the session API adds waaay too much work to bother implement it. Ideally I was hoping cf would just figure this out like turso does
CRight now I simply use cache & KV which give me pretty much the same results but it's simpler and easier to understand (I know it's eventually consistent, but that works for me)
LIf you are fine with normal eventual cache, then keep with that, and it fits better. Global consistency has tradeoffs, either exposed to the user and you decide the queries you want consistent, or it's always done implicitly and then you get slower performance across the board.
LWhich Turso feature specifically? I am aware of the embedded replicas but that's a whole other thing/use-case.
CThey used to have multi region replicas, but from the homepage it looks like they discontinue it
LIn what way is it too much work? It looks like it's a few lines of code tweak? That may be more work than continuing to use your own cache+KV solution, but for anyone who hasn't already built that, it seems like adopting the session API is a lot LESS work than building something like you've done.
CMaybe it's actually very little work, I've just quickly looked at the api, but it seems like I need to read incoming headers, tweak how drizzle interacts with the db, set a new header, etc.
With KV, I just do if (kv) return kn else return d1
The other advantage is that is not vendor lock in, I can switch to any other sqlite provider (like turso) with a single line change
With KV, I just do if (kv) return kn else return d1
The other advantage is that is not vendor lock in, I can switch to any other sqlite provider (like turso) with a single line change
Cbut anyways, I wasn't really complaining, I love d1 and cloudflare, was more like my personal feedback
BTangentially, hoping for DO dynamic relocation.
LYou mean relocation of the replicas in other places, or more replicas in specific places, or relocation of the primary?
And do you need it dynamic based on traffic/requests, or you specifying that?
And do you need it dynamic based on traffic/requests, or you specifying that?
BRelocation of the primary, either manually specify or automatic like worker smart placement.
BReplicas would be nice too but I imagine it would have a similar design to D1 so it would take some effort to make use of it.
IAnd here you go Zack, read replicas are here 
II was trying to give you a hint the other day without saying anything I wasn't allowed to :lul:
ZYea, it makes more sense now, but in a way that's slightly sad because the replicas are just statically placed in all regions rather than dynamically in more places based on load
ZHowever, very happy it's here, and sounds like dynamic placement is something they want to bring in the future 
IYeessss except:
currently one in each supported D1 regionSo right now they're static but they're static in everywhere D1 can even be
IIf they were dynamic they'd just be dynamic within those same regions.
ZYea, I get it
Zmuch nicer than having to place them in all regions ourselves, and as I said, improvements will come and will be great to see them!