This is part 2 of our expand and contract migration series, to be merged only after #1 is successfully deployed.
Now that we've made sure the application is writing to the new tables (in addition to the old ones) we can copy data into the new tables and be certain that they will be in sync with the old tables as part of the migration. Since the code changes in this PR will be deployed only after the migration succeeds, we can then immediately start reading exclusively from the new tables, which is what the rest of the changes in this PR accomplish:
There should be no more queries reading from the members, form_to_permissions, and permissions (writing is still ok)
Explicit typings using the generated Members types have been replaced with CommunityMemberships equivalents
Issue(s) Resolved
718
High-level Explanation of PR
This is part 2 of our expand and contract migration series, to be merged only after #1 is successfully deployed.
Now that we've made sure the application is writing to the new tables (in addition to the old ones) we can copy data into the new tables and be certain that they will be in sync with the old tables as part of the migration. Since the code changes in this PR will be deployed only after the migration succeeds, we can then immediately start reading exclusively from the new tables, which is what the rest of the changes in this PR accomplish:
members,form_to_permissions, andpermissions(writing is still ok)Memberstypes have been replaced withCommunityMembershipsequivalents