- From: Brett Zamir <notifications@github.com>
- Date: Sat, 11 Feb 2017 18:53:41 -0800
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 12 February 2017 02:54:20 UTC
Unless I'm missing a conceptual or anticipated reason for specifying the steps this way, I'd think that step 1 of the "steps for storing a record into an object store" routine (i.e., "If store uses in-line keys, run these substeps:") could be removed and thereby limit some redundancy by having `IDBCursor.update` set `key` to `kpk` in its "If the effective object store of this cursor uses in-line keys, run these substeps:" routine immediately preceding its call to the record storing steps (as do `IDBObjectStore.put` and `IDBObjectStore.add` in their equivalent, corresponding step preceding the record storing steps), and then supply that `key` instead of the effective key as `key` to the record storing steps in such a case. I know implementations could optimize the redundancy out anyways, but it seems it would be simpler conceptually as well unless I'm missing a reason for it. -- 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/144
Received on Sunday, 12 February 2017 02:54:20 UTC