Page MenuHomePhabricator

[web] switch code from `sql.js` API to `.wasm` database module
ClosedPublic

Authored by kamil on Jul 19 2023, 7:05 AM.
Tags
None
Referenced Files
F2157232: D8560.id29134.diff
Mon, Jul 1, 1:23 AM
F2157231: D8560.id29133.diff
Mon, Jul 1, 1:23 AM
F2157230: D8560.id29006.diff
Mon, Jul 1, 1:23 AM
F2157229: D8560.id28835.diff
Mon, Jul 1, 1:23 AM
F2157166: D8560.diff
Mon, Jul 1, 1:19 AM
F2153820: D8560.id29134.diff
Sun, Jun 30, 5:59 PM
Unknown Object (File)
Sat, Jun 29, 12:15 PM
Unknown Object (File)
Sat, Jun 29, 9:40 AM
Subscribers

Details

Summary

This is very important diff - it starts using .wasm API from SQLiteQueryExecutor instead of sql.js.

We do not have to migrate this content, we will simply take old content from indexedDB and put this to database module (schema is the same).

Depends on D8559

Test Plan

Test everything end-to-end.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Jul 19 2023, 9:11 AM

How does this interact with migrations?

EDIT: I talked with @kamil and the native migrations will just run and bump the db version to match the native. But it's fine because the schema between web and native is the same

web/database/worker/db-worker.js
234 ↗(On Diff #28835)

Is this needed?

This revision is now accepted and ready to land.Jul 24 2023, 5:35 AM
web/database/worker/db-worker.js
234 ↗(On Diff #28835)

it is not, good catch