I think I've found a bug in the SQLite
I think I've found a bug in the SQLite backend - calling
deleteAll() in an alarm handler results in an internal error, unless I call deleteAlarm() first6 Replies
I want to use alarms to delete all data, for eg a verify link that auto-expires. this seemed to work fine using the KV backend
when I tried it with the SQLite backend, I get an exception on the alarm handler and it keeps on trying. until I added a call to
deleteAlarm(), which seemed to fix it.
it's possible this is expected behaviour (and it's not a big deal to delete the alarm first), in which case the docs could be clearer - and this is a change compared to the KV versionI don't think this should be intended. Could you create an issue on the workerd github repo?
sure - would this be "runtime-apis
Report an issue with an API provided by workerd" ?
yeah I think so
this is a bug which we're aware of. There are a few issues around sqlite-backed DOs and alarms still. We are working through them.
oh! I've just filed a bug report https://github.com/cloudflare/workerd/issues/2993
GitHub
🐛 Bug Report — Runtime APIs - Durable Objects with SQLite storage -...
I think I've found a bug in the SQLite storage backend for Durable Objects. When I call deleteAll() from an alarm handler, it causes an internal error. Which means the alarm handler fails and k...