Integrate the contact revision in the main call log database and remove the async_storage uses

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
4 years ago
2 years ago

People

(Reporter: gsvelto, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
+++ This bug was initially created as a clone of Bug #1107781 +++

The call log currently uses two separate databases: the main call log database handled directly via IndexedDB and an async_storage-based database used only for storing the version of the contact database. This wastes resources for no good reason (we store two full DBs, need two DB connections with associated memory usage, etc...) and makes upgrading the call log DB fragile as we write updates to two different databases w/o synchronization between them and hope that things just work.

We should remove the async_storage uses & its associated database and merge the little data we store there into the main call log database. We should also fold the async_storage operations into the existing IndexedDB transactions thus making the updates fully atomic.
Created attachment 8594674 [details] [review]
[gaia] gabrielesvelto:bug-1156189-remove-async-storage > mozilla-b2g:master
(Reporter)

Comment 2

4 years ago
WIP PR attached.
(Reporter)

Updated

2 years ago
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.