Add foreign key relationship between SiteModel and NotificationModel #1285
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1284 by adding a foreign key for
local_site_id
that depends onSiteModel
. If the matching site is deleted, the records matching thatlocal_site_id
inNotificationModel
will deleted automatically.This PR includes:
NotificationModelBuilder
to add the foreign keyWellSqlConfig
to dropNotificationModel
on upgrade and recreate the table with the foreign keySiteModel
db dependency as well as a test to verify that theon delete cascade
worksDELETE FIRST SITE (DB ONLY)
button in the Sites section of the example app. This allows for testing by:NotificationModel
table using Stethos.