Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BE] Create a join model so request issues and decision issues can have many-to-many relationship #7884

Closed
anyakhvost opened this issue Nov 16, 2018 · 1 comment

Comments

@anyakhvost
Copy link

anyakhvost commented Nov 16, 2018

  1. Create a join model RequestDecisionIssue and the associated table.
  2. Start writing to the new table for HLR and SC as well as to the source_request_issue_id column
  3. Deploy
  4. Then write a migration to migrate existing decision_issues to use the new table
  5. Deploy
  6. Start reading from the new table for all cases
  7. Deploy
  8. Remove source_request_issue_id from the decision_issues
@pkarman
Copy link
Contributor

pkarman commented Nov 16, 2018

It seems important to be able to explicitly know if a RequestIssue is in response to a DecisionIssue (its "source") or vice versa. We might need additional column(s) on the join model in order to designate that relationship.

va-bot pushed a commit that referenced this issue Nov 16, 2018
This is the first PR for #7884

### Description
1. Create a join model RequestDecisionIssue and the associated table.
2. Start writing to the new table for HLR and SC as well as to the source_request_issue_id column
va-bot pushed a commit that referenced this issue Nov 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants