ISSUE-163 Data in iccat_gbyp0001_ArgosTrans_eTUFF.txt violates foreign key constraint histogrambindata_histogrambininfo_fkey #172
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
…n key constraint histogrambindata_histogrambininfo_fkey
lewismc
added
bug
lewismc
added a commit
that referenced
this pull request
Sep 24, 2023
…n key constraint histogrambindata_histogrambininfo_fkey (#172)
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.
Addresses #163
There was an error in the legacy
iccat_gbyp0001_ArgosTrans_eTUFF.txtas explained however this was rectified/corrected in theiccat_gbyp0008_eTUFFreplacement. Essentially dummy datetime values are provided so atleast the TRIGGER logic can execute and complete successfully.