Refactor user_id
column type from unsignedInteger
to unsignedBigInteger
#392
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.
In this pull request, the
user_id
column in the migration file has been updated fromunsignedInteger
tounsignedBigInteger
. This change ensures better compatibility, especially when theid
column in theusers
table is of typeunsignedBigInteger
.The reason for this change is to handle larger integer values and to prevent potential issues when referencing the
users
table withBIGINT
primary keys. It also aligns with Laravel's default use ofunsignedBigInteger
for theid
column in theusers
table, ensuring proper foreign key relationships.This update is backward-compatible as the column remains
nullable
, and no additional changes to the database structure are required beyond this modification.