i feel more comfortable using the sync api mostly because the underlying sqlite engine is sync and i'm good with the trade-offs cloudflare ended up. also, i'm not sure if there's any performance implications with drizzle async api

yeah, basically it. That tell the worker to block all requests until the migrations have ran.

ya, i've been using DO sqlite for some time now, my question was mostly directed to drizzle interface being async when the underlying storage is sync, but i just found out about drizzle's sync api interface (.run, .values, .all, .get), etc.

now that you are here, is there any reason why drizzle API is async when the DO sqlite is sync?

don't you need to block concurrency when running migrations? like, wouldn't you have a problem if you get two calls to the same DO while running the migrations?

TIL that there was a drizzle adapter for DO, time to migrate all my sql to drizzle haha