W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

Re: [IndexedDB] What should be allowed as a key path?

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 8 Mar 2011 12:11:55 -0800
Message-ID: <AANLkTi=AhNvxgXAWFu_Ewxcn5Ubk205g_6DRKcH9ZAy5@mail.gmail.com>
To: Jeremy Orlow <jorlow@chromium.org>
Cc: public-webapps WG <public-webapps@w3.org>
On Mon, Mar 7, 2011 at 10:21 PM, Jeremy Orlow <jorlow@chromium.org> wrote:
> As far as I recall, we never settled on how key path should be specified.
>  Right now in Chrome, we allow any combination of .'s and static array
> lookups.  So, for example, we allow "foo.bar[1][2].baz".  I don't remember
> any specific use cases for the array lookups though, so I'm wondering if we
> should just specify "<property> ["." <property>]*" to be the key path
> specification.  Where <property> is whatever's allowed in JavaScript.  It
> seems to me that this should support most use cases, should be easy to
> understand and implement, and should leave us a lot of flexibility to
> support other use cases as we may come up with them.
> Thoughts?

This sounds good to me.

/ Jonas
Received on Tuesday, 8 March 2011 20:12:58 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:43 GMT