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

[Bug 15927] New: [IndexedDB] Allowing "." and " " in keys specified using keyPath

From: <bugzilla@jessica.w3.org>
Date: Tue, 07 Feb 2012 14:18:33 +0000
To: public-webapps@w3.org
Message-ID: <bug-15927-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15927

           Summary: [IndexedDB] Allowing "." and " " in keys specified
                    using keyPath
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
        AssignedTo: dave.null@w3.org
        ReportedBy: odinho@opera.com
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


I've been trying to find any decision/answer about IndexedDB keypath and "." to
seperate objects.

It's very possible I could get data from a third party that has:

   obj["my.key"] = thing

and I'd want to have a keypath that accesses  my.key  like that, so NOT like:

  obj = { my: { key: thing } }


Similarly about spaces:  obj["my key"] = "blabla"



It would introduce some extra complexity to support this, sure, and it might
not be worth it at all, but has it been discussed on its own?

-- 
Configure bugmail: https://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, 7 February 2012 14:20:15 GMT

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