1 Reply
I've already built my own SQLite bindings (which I actually prefer over the PR example), so I'll likely stick with mine. That said, full exposure of Workflows would be fantastic. One feature I think should be added fundamentally is the ability to apply migrations to the SQLite database for each Durable Object. I just finished porting the D1 migration pattern to my SQLite setup for Durable Objects, and it works great—essential for getting the full power of per-instance databases. I suspect most people just treat it as a KV store because versioning it per instance (plus handling DO tags) isn’t easy.