W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2010

[Bug 11269] New: Evaluating keyPaths needs to be better specified

From: <bugzilla@jessica.w3.org>
Date: Tue, 09 Nov 2010 00:38:52 +0000
To: public-webapps@w3.org
Message-ID: <bug-11269-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11269

           Summary: Evaluating keyPaths needs to be better specified
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
        AssignedTo: dave.null@w3.org
        ReportedBy: jonas@sicking.cc
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


This bug is very similar to bug 9832, however since that bug is discussing a
lot of related issues, I wanted to file a separate one to make sure this isn't
forgotten.

Currently the syntax for parsing a keyPath isn't explicitly defined. It is
clear that for keypath/object

"foo.bar.baz"
{ foo: { bar: { baz: 4 } } }

the result is 4. However does keypath/object

"foo[1].bar"
{ foo: [ false, { bar: 4 }, true ] }

evaluate to 4? What about

"foo[x].bar"
{ foo: [ { bar: 4 } ], x: 0 }

or

""
4

Do either of those evaluate to 4? The last example could be useful when
out-of-line keys are used, but still wanting to be able to search on the stored
value.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 9 November 2010 00:38:54 GMT

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