Fix: Handle registration error during initial deployment due to missing 'users' table #269
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.
Link issue: #262
Problem Description:
During the initial deployment, attempting to register as a user results in an error. This is because the necessary 'users' table is missing from the PostgreSQL database.
Solution:
I have added a check to verify the existence of the 'users' table. If the table does not exist, I create the 'users' table to resolve this issue.
Details of the Changes:
Added a function checkIfUsersTableExists() to check if the 'users' table exists.
If the 'users' table does not exist, it is created.
Testing Results:
I have tested this modification in my local environment to ensure that the registration functionality works correctly during the initial deployment.