The database column social_id was too short to accept tokens from Google. The column size has been increased to accommodate the full length of Google tokens.
Related Issue (Link to Github issue)
Motivation and Context
The social_id column was previously defined with a size that was too short to store Google tokens. This caused errors when attempting to store tokens, resulting in issues with user authentication and registration. Increasing the column size resolves this issue and ensures compatibility with the full length of Google tokens.
Screenshots (if appropriate - Postman, etc):
How Has This Been Tested?
Testing Environment: The issue was tested in a development environment with a MySQL database.
Tests Run:
Updated the column size in the database schema.
Validated that tokens of various lengths, including those from Google, are now stored correctly.
Verified that user registration and authentication processes work as expected with Google tokens.
Ensured that no other functionality was affected by the schema change.## Screenshots (if appropriate - Postman, etc):
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Description
The database column social_id was too short to accept tokens from Google. The column size has been increased to accommodate the full length of Google tokens.
Related Issue (Link to Github issue)
Motivation and Context
The
social_idcolumn was previously defined with a size that was too short to store Google tokens. This caused errors when attempting to store tokens, resulting in issues with user authentication and registration. Increasing the column size resolves this issue and ensures compatibility with the full length of Google tokens.Screenshots (if appropriate - Postman, etc):
How Has This Been Tested?
Testing Environment: The issue was tested in a development environment with a MySQL database.
Tests Run:
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.