refactor(Subscription): rename columns and adjust primary/foreign keys #2298
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.
This PR updates the
Subscription
table to get it more closely aligned with Laravel best practices.A migration has been added which performs the following:
[SubjectType, SubjectID, UserID]
primary key.id
column as the new primary key.SubjectType
->subject_type
SubjectID
->subject_id
UserID
->user_id
State
->state
Created
->created_at
Updated
->updated_at
user_id
to an unsigned big integer.[subject_type, subject_id, user_id]
.user_id
toUserAccounts.ID
.Subscription
tosubscriptions
.Additionally, the
Subscription
andUser
Eloquent models have been updated.