W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

Re: [IndexedDB] Should .add/.put/.update throw when called in read-only transaction?

From: Jonas Sicking <jonas@sicking.cc>
Date: Fri, 2 Jul 2010 13:45:24 -0700
Message-ID: <AANLkTikPrzlQhZnjj4DxB_XP4iDOuA5A46Cuw2bdgxpn@mail.gmail.com>
To: Andrei Popescu <andreip@google.com>
Cc: Jeremy Orlow <jorlow@chromium.org>, ben turner <bent@mozilla.com>, Webapps WG <public-webapps@w3.org>
On Fri, Jul 2, 2010 at 1:02 PM, Andrei Popescu <andreip@google.com> wrote:
> On Fri, Jul 2, 2010 at 10:43 AM, Jonas Sicking <jonas@sicking.cc> wrote:
>> Filed http://www.w3.org/Bugs/Public/show_bug.cgi?id=10064
> Fixed. Please have a look, in case I missed or got anything wrong. Thanks!

For add and put you should not throw DATA_ERR if the objectStore has a
key generator.

It would be ideal if we don't have to define our own error for when
cloning fails, but instead be consistent with other APIs that use
structured clones. However right now the error thrown by the HTML5
spec is pretty useless, I filed [1] on that against the HTML5 spec.

[1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=10069

Looks great otherwise, thanks!

/ Jonas
Received on Friday, 2 July 2010 20:46:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:09 UTC