Opened 5 months ago

Closed 3 months ago

#7342 closed change (fixed)

Remove the code handling the data migration from ioIndexedDB

Reported by: geo Assignee: geo
Priority: P2 Milestone: Adblock-Plus-for-Chrome-Opera-Firefox-next
Module: Platform Keywords:
Cc: sebastian, kzar Blocked By:
Blocking: Platform: Edge
Ready: yes Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

https://gitlab.com/eyeo/adblockplus/adblockpluschrome/merge_requests/47

Description (last modified by sebastian)

Background

With 6621 we started using IndexedDB directly and added a migration path from localforage (used in 0.9.11 and before). With 6775 we implemented a backup strategy in order to deal with the volatile properties of IndexedDB, which added further complexity to the migration path.

By the time 0.9.15 will be releases we assume that the vast majority of users are no longer on a version that uses localForage (i.e. <=0.9.11), so that we can simplify the code path by removing the migration logic, which in turn might also make data storage more reliable as some users are still reporting data corruptions.

What to change

Remove the code handling the migration from localForage in ioIndexedDB.

Change History (5)

comment:1 Changed 5 months ago by sebastian

  • Description modified (diff)
  • Priority changed from Unknown to P2
  • Ready set

comment:2 Changed 4 months ago by geo

  • Owner set to geo

comment:3 Changed 4 months ago by geo

  • Review URL(s) modified (diff)

comment:4 Changed 4 months ago by abpbot

comment:5 Changed 3 months ago by geo

  • Milestone set to Adblock-Plus-for-Chrome-Opera-Firefox-next
  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.