- From: Joshua Bell <notifications@github.com>
- Date: Fri, 20 Jan 2017 08:52:22 -0800
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 20 January 2017 16:53:05 UTC
Key order can't be changed, so your choices today are more careful querying or modifying the data before it is indexed. "Order by A ascending, B descending" is a pain. Easiest (I think) is an index on A, and a compound key index [A,B]; do a unique cursor walk over A and for each A found use another cursor with a prefix range in reverse order on the compound index. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/IndexedDB/issues/138#issuecomment-274121427
Received on Friday, 20 January 2017 16:53:05 UTC