pretty sure calling it with 128 keys
pretty sure calling it with 128 keys multiple times over will still be single transaction as long as you dont await, otherwise its probably not possible
5 Replies
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
It is possible given the new sync method added its no longer the case you cant await the storage op, but to be extra sure you could submit an issue for extra clarification: https://github.com/cloudflare/cloudflare-docs/issues
GitHub
Issues · cloudflare/cloudflare-docs
Cloudflare’s documentation. Contribute to cloudflare/cloudflare-docs development by creating an account on GitHub.
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
ok thanks, that's really helpful to know - i'll stick with explicit txns then, at least have up to 128. Would love to see that limit increased in any amount - there are a few spots that I'm writing data records + assoc index records, or deleting a parent record + multiple child records that while sometimes can fit in 128, can exceed it as well - leaving the system potentially open to orphan records etc in the unlucky case
since DO storage is so simple, often what would be one sql "insert" or "delete" consists of more than one DO put, since we have to maintain the indexes ourselves - so the ability to fit more in a single transaction would mean the ability to do more logical operations in a single atomic call
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View