On Thu, Jul 7, 2011 at 1:46 PM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Jul 6, 2011 at 9:41 PM, Jeremy Orlow jor...@chromium.org wrote:
On Wed, Jul 6, 2011 at 10:06 AM, Israel Hilerio isra...@microsoft.com
We believe an error should be thrown because of the violation of the
unique
On Wed, Jul 6, 2011 at 10:06 AM, Israel Hilerio isra...@microsoft.com wrote:
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
On Wed, Jul 6, 2011 at 9:41 PM, Jeremy Orlow jor...@chromium.org wrote:
On Wed, Jul 6, 2011 at 10:06 AM, Israel Hilerio isra...@microsoft.com
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.
On Thursday, July 07, 2011 1:46 PM, Jonas Sicking wrote:
On Wed, Jul 6, 2011 at 9:41 PM, Jeremy Orlow jor...@chromium.org
wrote:
On Wed, Jul 6, 2011 at 10:06 AM, Israel Hilerio
isra...@microsoft.com
We believe an error should be thrown because of the violation of the
unique value index
On Thu, Jul 7, 2011 at 6:35 PM, Israel Hilerio isra...@microsoft.com wrote:
On Thursday, July 07, 2011 1:46 PM, Jonas Sicking wrote:
On Wed, Jul 6, 2011 at 9:41 PM, Jeremy Orlow jor...@chromium.org
wrote:
On Wed, Jul 6, 2011 at 10:06 AM, Israel Hilerio
isra...@microsoft.com
We believe an
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
On Wed, Jul 6, 2011 at 10:06 AM, Israel Hilerio isra...@microsoft.comwrote:
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
