Add unique constraint to Hacker and update relations #66
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit ensures that each hacker-user pairing for a hackathon is unique by adding a new unique constraint on the `Hacker` table. It also modifies the `User` model to reflect a one-to-many relationship with `Hacker` instead of a one-to-one relationship.
The unique constraint on the combined fields userId and hackathonId in the HackerApplication model has been removed. This change allows for multiple entries with the same userId and hackathonId combination. The modification addresses issues related to duplicative data entries for users in the same hackathon.
This commit drops the unique index "Hacker_userId_hackathonId_key". This change allows multiple records with the same combination of userId and hackathonId.
Ensure unique constraint on userId and hackathonId columns. This prevents duplicate entries and enforces data integrity for hacker-hackathon pairs.
Added hackathonId parameter to getApplicationFormStep function to better filter hacker records. This change ensures that hackers are correctly associated with their respective hackathons.
Integrated the retrieval of the active hackathon ID into hacker session validation and form step data fetching. This ensures that operations are scoped to the current active hackathon.
Removed unnecessary hackathon ID check in requireHackerSession and updated query to order by creation date. Enhanced isApplicationComplete to include detailed application and hacker validation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 commit ensures that each hacker-user pairing for a hackathon is unique by adding a new unique constraint on the
Hackertable. It also modifies theUsermodel to reflect a one-to-many relationship withHackerinstead of a one-to-one relationship.