-
Notifications
You must be signed in to change notification settings - Fork 40
Skip on existing Splocalecontaineritem instead of Splocalecontainer #7562
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
Conversation
Triggered by c6300f1 on branch refs/heads/issue-7559
Triggered by 5c9b0d4 on branch refs/heads/issue-7559
|
|
||
| const isLoanReturnLike = | ||
| isLoanReturn || (actionTable.name !== 'Loan' && actionTable.name.includes('Loan')); | ||
| isLoanReturn || |
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.
Why does this PR reformat this?
grantfitzsimmons
left a comment
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.
I have a database (shared with Alec) that is missing agent3, agent4, and agent5 in the Loan table after running ve/bin/python manage.py run_key_migration_functions. This is not handled in this PR, resulting in an incomplete schema. This fixes the missing tables and fields for 7-only tables, but not if a discipline was added after we added fields to an existing table.
|
This PR will be handled in the #7672 PR |
Fixes #7559
Skip on existing Splocalecontaineritem instead of Splocalecontainer. This works on the example workshop database. More testing to be done on other databases.
Checklist
self-explanatory (or properly documented)
Testing instructions
ve/bin/python manage.py run_key_migration_functionsDjango command runs before testing.