Issue
We generate and store pattern which are processed locally and downloaded from cloud.
There is this problem that downloaded database can overwrite popularity of locally generated pattern's popularity. This can cause problem if locally generated pattern popularity is latest and accurate compare to cloud supplied data.
This happens because we are using dexie-import-export package to import large size database without using a lot of memory. Right now there is no way to make a filter to solve this problem.
Reported issue: dexie/Dexie.js#1008
Expected Behavior
Database popularity should only be updated if newly supplied value is latest(bigger) compare to stored popularity of any pattern.
Issue
We generate and store pattern which are processed locally and downloaded from cloud.
There is this problem that downloaded database can overwrite popularity of locally generated pattern's popularity. This can cause problem if locally generated pattern popularity is latest and accurate compare to cloud supplied data.
This happens because we are using dexie-import-export package to import large size database without using a lot of memory. Right now there is no way to make a filter to solve this problem.
Reported issue: dexie/Dexie.js#1008
Expected Behavior
Database popularity should only be updated if newly supplied value is latest(bigger) compare to stored popularity of any pattern.