David Fahlander

orderBy is basically iterating the index. But it sounds like the unique flag is set on the collection when you do the ordering. Try whether the call to eachUniqueKey() could...

Could we use a simpler approach and just allow an optional `name` property? I suppose letting the name depend on the other info from the file is less common use...

This PR can probably be closed but kept as a reference to what could be doable. The problem with this could be that it uses template strings and conditionals too...

You can get an observable and all if you could change your model to let a file be represented by a row in a single db instead. (And you'd get...

EntityTable currently only supports single property primary keys. Try with `Table` instead

Dexie does not have any explicit foreign keys nor automatic cascade deletion. But it has ACID consistency so you can easily create a service method or function `deleteAuthor()` that deletes...

Cascading deletes are only relevant in hierarchial structures. One useful pattern for this that I have been advocating for, is to use a `parentPath` property on the objects define the...

Traditional cascading deletes can be implemented using DBCore as follows: 1. Create a [DBCore](https://dexie.org/docs/DBCore/DBCore#definition) middleware and override `transaction` and `table` 2. In `transaction` make sure to always include related tables...

Thanks. This seem to be a completion of #2155 for the other hooks.

liveQuery() does not emit anything until a query finish. If arguments change and you gain a new store, Svelte will keep showing the value from the previous store until the...