IndexedDB Transactions: The Gatekeepers of Data
An IndexedDB transaction is a short-lived container for all database operations, ensuring data integrity. Use it for any read or write. The main footgun: transactions auto-commit if idle, so you must queue all requests synchronously without waiting.
An IndexedDB transaction is a short-lived container for all database operations, ensuring data integrity by grouping reads and writes. You start a transaction, get a reference to an object store, and then make requests. The main footgun is its lifecycle: a transaction auto-commits once all its requests are done and no new ones are queued synchronously. If you `await` a non-IDB promise mid-transaction, it will close prematurely, causing subsequent requests to fail.
Read the original → developer.mozilla.org
- #indexeddb
- #web apis
- #transactions
- #browser storage
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.