ACTUALL FIX: Forget about previous commits. #71
Merged
+337
−6
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
…ating charities a *Random UUID*. When running it again same API-object turned into charities will have different UUID, breaking foreign key contraint. This is why when there are no tables it will work (cuz it gets inserted for the first time) and doesnt work on the second (now inserting the same api data, with different UUID).
Sign in
to join this conversation on GitHub.
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 is the fix: When creating charities a Random UUID. When running it again same API-object turned into charities will have different UUID (in APICharityScraper + Charity), breaking foreign key contraint. This is why when there are no tables it will work (cuz it gets inserted for the first time) and doesnt work on the second (now inserting the same api data, with different UUID).