Radek Pietruszewski

> These two restrictions happen because the "mega chunks" part use IDB's key ranges (and maybe for other reasons I can't remember atm). makes sense. You could always disable the...

> Yeah. From my preliminary measurements, using crypto-js's Rabbit algorithm, IDB storage consumption increased by ~650% [9mb to 68mb after that test file that does fuzz tests and whatnot] and...

> Good! What are the next steps, you'd say? Send a pull request to Nozbe/LokiJS with the required hooks and some tests (tests don't need to have real encryption used...

@acdcjunior even if it's not mergeable or reviewable, it might help others, so do share ;)

Nice! Thank you for your contribution! Some quick thoughts: - `getSyncChanges` provides summary of migration changes via sync to backend. The purpose of that is to allow server to update...

> It looks like ALTER TABLE DROP COLUMN is not supported although the docs say it does on which platform are you testing that?

oh no https://sqlite.org/changes.html this was only added in 3.35.0 :(

you could go with something like this : https://stackoverflow.com/questions/5938048/delete-column-from-sqlite-table but you probably have to drop and recreate indices for it to work

@bmatasar Unfortunately, it's complicated. On iOS and Android we're using the system built-in version of sqlite, so we can't rely on newer sqlite features. On Android JSI we're bundling sqlite...

yeah that's fair. I forgot about this, but this difficulty is why I never implemented dropping tables and columns in migrations - it shouldn't be very hard but it's not...