Re: [w3c/IndexedDB] Proposal: Add "writeonly" transaction mode (#234)

Given that the main benefit here is performance, I agree `commit()` may be a more direct way of tackling this problem. Adding a special mode where you can only write and can't respond to individual constraint errors may be of limited value, although it is perfect for initial database setup scenarios such as #224.

If the core performance issue is that creating too many callbacks in the form of multiple `put()`s causes overhead, I also think `putAll()` (returning some kind of array of results/errors) may also be an interesting option here.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/234#issuecomment-391109023

Received on Tuesday, 22 May 2018 19:17:06 UTC