Replace Notification Database with Service Worker Database
 

Currently, there are two databases, the notification database and the service worker database. There is some degree of redundancy between them, and in combining the databases, we can remove a data storage source, the data that has to be stored and clean up the notification database code.

The notification database stores information about the notification itself and the service worker it is tied to. Since each notification is tied to exactly one service worker, combining the databases will remove duplicate storage. Functions that operate on all the notifications tied to a service worker can also be removed, as all notifications will be grouped by service worker in the service worker database. This will mean we can clean up the existing code.

The present notification database also stores a persistent notification id, which will be moved to the profile as it needs to persist across restarts.
 

Currently, there are two databases, the notification database and the service worker database. There is some degree of redundancy between them, and in combining the databases, we can remove a data storage source, the data that has to be stored and clean up the notification database code.

The notification database stores information about the notification itself and the service worker it is tied to. Since each notification is tied to exactly one service worker, combining the databases will remove duplicate storage. Functions that operate on all the notifications tied to a service worker can also be removed, as all notifications will be grouped by service worker in the service worker database. This will mean we can clean up the existing code.

The present notification database also stores a persistent notification id, which will be moved to the profile as it needs to persist across restarts.

Information about existing functions and what will have to change here: https://docs.google.com/document/d/1mrQEIjOittDZ-sRPKRW_6S5-j112idSSTnQxT9kUpmM/edit?usp=sharing