IndexedDB does not support complex keys - by Nolan Lawson

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

ID 866474 Comments
Status Closed Workarounds
Type Bug Repros 5
Opened 5/3/2014 11:53:22 AM
Access Restriction Public


IndexedDB v1 is supposed to support both strings and arrays of strings as keys.  In IE, however, arrays of strings are not permitted as keys and instead throw an error.
Sign in to post a comment.
Posted by Microsoft on 4/4/2016 at 11:35 AM
We've moved! This issue is now being tracked at
Posted by JacoSchutte1234 on 10/30/2015 at 7:52 AM
Unfortunately the same issue still persists in Microsoft Edge, quite some time later :/. I'm unable to support Windows 10 universal apps (using cordova) due to this limitation. Our applications makes extensive use of complex keys in indexeddb.
Posted by Nolan Lawson on 7/2/2015 at 12:07 PM
Thanks! Really glad to hear that. :)
Posted by Charles Morris [MSFT] on 6/30/2015 at 12:27 PM
Just a quick update to say this is still something that we are tracking on our backlog.
Posted by Microsoft on 5/5/2014 at 10:39 AM
Thank you for your feedback!

We will be investigating this issue further.

Best Regards,
The Internet Explorer Team