-
Notifications
You must be signed in to change notification settings - Fork 16
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
[Issue #2123] Add Opportunity Attachment and Lookup Tables #2483
[Issue #2123] Add Opportunity Attachment and Lookup Tables #2483
Conversation
Co-authored-by: Michael Chouinard <[email protected]>
Co-authored-by: Michael Chouinard <[email protected]>
opportunity_id: Mapped[int] = mapped_column( | ||
BigInteger, ForeignKey(Opportunity.opportunity_id), primary_key=True, index=True | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missed this the first time, we don't need opportunity ID to be a part of the primary key here I don't think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, makes sense. Made that change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Summary
Fixes #2123
Time to review: 10 mins
Changes proposed
Context for reviewers
See generated migration and screenshots of result after db upgrade.
Only the created_by, updated_by, and legacy_folder_id columns should be nullable.
Additional information
Screenshots of new tables after running
make db-upgrade