rockerest’s Twitter Archive—№ 16,754

…in reply to @schizanon
@yesiwebto I think Dexie's compound index support would allow something but I'm not 100% sure how. It's definitely in here somewhere: dexie.org/docs/Compound-Index#matching-first-part-only
Permalink On twitter.com 2021 Jul 21 Mood +3 🙂

…in reply to @rockerest
@yesiwebto Oh yeah I think what you posted is right. Dexie creates a virtual index on the parts of the compount indexes, so yes I think what you posted is how you'd query with an OR on the two parts of the compound index.
Permalink On twitter.com ❤️ 1 Favorite 2021 Jul 21 Mood +2 🙂

…in reply to @rockerest
@yesiwebto The chaining seems to break down after the first .where, which is frustrating, but I think you could simplify a bit like: .where( { fileName } ) .or( "otherFileName" ) .equals( fileName );
On twitter.com 2021 Jul 21 Mood 0

…in reply to @rockerest
@yesiwebto (frustrating, because I want it to be: .where( { fileName } ) .or .where( { "otherFileName": fileName } ); que sera)
Permalink On twitter.com 2021 Jul 21 Mood -1 🙁

…in reply to @rockerest
@yesiwebto ... calling .where immediately returns a Collection, and then calling .or returns a new WhereClause. .where returning a Collection right away is the original sin. We should be able to build up a big query before converting it to a Collection - either explicitly or implicitly.
Permalink On twitter.com ❤️ 1 Favorite 2021 Jul 21 Mood -1 🙁

…in reply to @rockerest
@yesiwebto Anyway, I'm just rabbit-trailing now :)
Permalink On twitter.com 2021 Jul 21 Mood 0