Re: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-25 Thread Jonas Sicking
On Wed, Jan 25, 2012 at 11:38 AM, Joshua Bell wrote: > On Tue, Jan 24, 2012 at 11:38 AM, Jonas Sicking wrote: >> >> On Tue, Jan 24, 2012 at 8:43 AM, Joshua Bell wrote: >> > On Tue, Jan 24, 2012 at 2:21 AM, Jonas Sicking wrote: >> >> What happens if a value "higher up" in the keyPath is not an o

Re: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-25 Thread Joshua Bell
On Tue, Jan 24, 2012 at 11:38 AM, Jonas Sicking wrote: > On Tue, Jan 24, 2012 at 8:43 AM, Joshua Bell wrote: > > On Tue, Jan 24, 2012 at 2:21 AM, Jonas Sicking wrote: > >> What happens if a value "higher up" in the keyPath is not an object: > >> store = db.createObjectStore("os", { keyPath: "a.

Re: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-24 Thread Jonas Sicking
On Tue, Jan 24, 2012 at 5:28 PM, Joshua Bell wrote: > > > On Tue, Jan 24, 2012 at 5:15 PM, Jonas Sicking wrote: >> >> On Tue, Jan 24, 2012 at 4:23 PM, Joshua Bell wrote: >> > >> > >> > On Tue, Jan 24, 2012 at 4:16 PM, Israel Hilerio >> > wrote: >> >> >> >> On Tuesday, January 24, 2012 11:38 AM,

Re: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-24 Thread Joshua Bell
On Tue, Jan 24, 2012 at 5:15 PM, Jonas Sicking wrote: > On Tue, Jan 24, 2012 at 4:23 PM, Joshua Bell wrote: > > > > > > On Tue, Jan 24, 2012 at 4:16 PM, Israel Hilerio > > wrote: > >> > >> On Tuesday, January 24, 2012 11:38 AM, Jonas Sicking wrote:> > >> > Based on this (pending details from mi

Re: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-24 Thread Jonas Sicking
On Tue, Jan 24, 2012 at 4:23 PM, Joshua Bell wrote: > > > On Tue, Jan 24, 2012 at 4:16 PM, Israel Hilerio > wrote: >> >> On Tuesday, January 24, 2012 11:38 AM, Jonas Sicking wrote:> >> > Based on this (pending details from microsoft of course) I suggest the >> > following set of steps: >> > >> >

Re: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-24 Thread Joshua Bell
On Tue, Jan 24, 2012 at 4:16 PM, Israel Hilerio wrote: > On Tuesday, January 24, 2012 11:38 AM, Jonas Sicking wrote:> > > Based on this (pending details from microsoft of course) I suggest the > > following set of steps: > > > > 1. If /keyPath/ is the empty string, skip the remaining steps and > /

RE: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-24 Thread Israel Hilerio
On Tuesday, January 24, 2012 11:38 AM, Jonas Sicking wrote: > On Tue, Jan 24, 2012 at 8:43 AM, Joshua Bell wrote: > > On Tue, Jan 24, 2012 at 2:21 AM, Jonas Sicking wrote: > >> > >> On Mon, Jan 23, 2012 at 5:34 PM, Joshua Bell > wrote: > >> > There's another edge case here - what happens on a pu

Re: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-24 Thread Jonas Sicking
On Tue, Jan 24, 2012 at 8:43 AM, Joshua Bell wrote: > On Tue, Jan 24, 2012 at 2:21 AM, Jonas Sicking wrote: >> >> On Mon, Jan 23, 2012 at 5:34 PM, Joshua Bell wrote: >> > There's another edge case here - what happens on a put (etc) request to >> > an >> > object store with a key generator when t

Re: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-24 Thread Joshua Bell
On Tue, Jan 24, 2012 at 2:21 AM, Jonas Sicking wrote: > On Mon, Jan 23, 2012 at 5:34 PM, Joshua Bell wrote: > > There's another edge case here - what happens on a put (etc) request to > an > > object store with a key generator when the object store's key path does > not > > yield a value, yet th

Re: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-24 Thread Jonas Sicking
On Mon, Jan 23, 2012 at 5:34 PM, Joshua Bell wrote: > There's another edge case here - what happens on a put (etc) request to an > object store with a key generator when the object store's key path does not > yield a value, yet the algorithm below exits without changing the value. > > Sample: > >

Re: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-23 Thread Joshua Bell
There's another edge case here - what happens on a put (etc) request to an object store with a key generator when the object store's key path does not yield a value, yet the algorithm below exits without changing the value. Sample: store = db.createObjectStore("my-store", {keyPath: "a.b", autoInc

Re: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-11 Thread Joshua Bell
I thought this issue was theoretical when I filed it, but it appears to be the reason behind the difference in results for IE10 vs. Chrome 17 when running this test: http://samples.msdn.microsoft.com/ietestcenter/indexeddb/indexeddb_harness.htm?url=idbobjectstore_add8.htm If I'm reading the test

RE: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-11 Thread Israel Hilerio
Great! I will work with Eliot to unify the language and update the spec. Israel On Wednesday, January 11, 2012 3:45 PM, Joshua Bell wrote: On Wed, Jan 11, 2012 at 3:17 PM, Israel Hilerio mailto:isra...@microsoft.com>> wrote: We updated Section 3.1.3 with examples to capture the behavior you are

Re: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-11 Thread Joshua Bell
). We should unify the language; I'm not sure if there's precedent for one step vs. two step attribute assignment. > ** > > Israel > > ** ** > > On Wednesday, January 11, 2012 12:42 PM, Joshua Bell wrote: > > *From:* jsb...@google.com [mailto:jsb

RE: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-11 Thread Israel Hilerio
bject: Re: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value On Wed, Jan 11, 2012 at 12:40 PM, Joshua Bell mailto:jsb...@chromium.org>> wrote: I thought this issue was theoretical when I filed it, but it appears to be the reason behind the difference in results fo

Re: [Bug 15434] New: [IndexedDB] Detail steps for assigning a key to a value

2012-01-11 Thread Joshua Bell
On Wed, Jan 11, 2012 at 12:40 PM, Joshua Bell wrote: > I thought this issue was theoretical when I filed it, but it appears to be > the reason behind the difference in results for IE10 vs. Chrome 17 when > running this test: > > > http://samples.msdn.microsoft.com/ietestcenter/indexeddb/indexeddb