[indexeddb] Calling update on a cursor index with a unique value constraint from Israel Hilerio on 2011-07-06 (public-webapps@w3.org from July to September 2011)

From: Israel Hilerio <israelh@microsoft.com>
Date: Wed, 6 Jul 2011 17:06:25 +0000
To: "public-webapps@w3.org" <public-webapps@w3.org>
CC: Adam Herchenroether <aherchen@microsoft.com>
Message-ID: <F695AF7AA77CC745A271AD0F61BBC61E3D189189@TK5EX14MBXC119.redmond.corp.microsoft.>

What is the expected behavior when calling update() in a cursor index that requires unique values.  Firefox allows the update, even when it results in a duplicate value.  Chrome throws an error event with the code set to UNKNOWN_ERR.

We believe an error should be thrown because of the violation of the unique value index constraint and the error code should be set to CONSTRAINT_ERR.  What do you think?

Israel

Received on Wednesday, 6 July 2011 17:07:06 UTC