Open
Conversation
21 tasks
Member
Author
|
Update -- testing this PR on the Review app, indeed the rake task aborts because of the same foreign key constraint issue. So a next step would be to find out which registers are still referencing non-validated plays, and remap them to validated ones. |
Contributor
|
Hi Jamie - It may help to know that the warehouse plays_dim table uses the same ids as the original plays table. Here are the bad plays: And, the bad register entries: Hope this helps! C |
Member
Author
|
@christopheryork -- Yep, that makes sense. I will request an update from Sara as to which plays those registers should point to instead. Thanks for confirming, and for those queries! |
Contributor
|
Sounds good. Good luck! |
This file contains hidden or 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
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 filters out play which are not expert_validated when the warehouse script is run.
It occurs to me that there could be a related problem in which existing tickets sales, or registers, are still referring to these non-expert validated plays, and which therefore need to be re-mapped to their expert validated equivalents.
I will (and you can) test the PR without affecting the staging or production databases, run the warehouse rake task on this heroku app: https://dashboard.heroku.com/apps/cfrp-staging-pr-3