Re: [w3c/IndexedDB] Combining cursors / query execution engine (#298) from Andrew Sutherland on 2020-03-09 (public-webapps-github@w3.org from March 2020)

From: Andrew Sutherland <notifications@github.com>
Date: Mon, 09 Mar 2020 13:51:08 -0700
To: w3c/IndexedDB <IndexedDB@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/IndexedDB/issues/298/596772817@github.com>

In our IndexedDB/Storage discussions at TPAC 2019 there was a level of consensus that for complicated storage use-cases, WASM supported by (potentially new) block storage primitives is indeed the way to go.

For those cases where SQLite-in-WASM/Lucene-in-WASM/etc. and their download dependencies are not necessary or desirable, IndexedDB can still make sense.  And for those cases, it's best for performance if the execution of the join logic can be pushed as close to the database as possible, avoiding content logic having to perform the join in userland (where existing code is currently having to do it).

-- 
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/298#issuecomment-596772817

Received on Monday, 9 March 2020 20:51:19 UTC