Old structure:
The old ProgrammeMembership table structure was :
and the programmeMemberships under People menu in TIS are like (the user shown below are mocked instead of real user data):
So from above, we can see a person can have multiple programmeMemberships, and a programmeMembership can have multiple curriculumMemberships. But the old table has all information together, which means the table has lots of redundant programmeMembership data for curriculumMembersihp against one programmeMembership.
Under the old table structure, when we need to extract a real programmeMembership, we use personId
, programmeStartDate
, programmeEndDate
, programmeId
, programmeMembershipType
fields for identification. When there’s a field above with missing data(data issue), some problems occurs for querying all curriculum memberships against a specific programmeMembership.
Why the refactoring is necessary?
Distinction between 2 entities
Current(new) table structure:
Steps:
To avoid thinking of naming of some interim tables, we decided to:
Rename ProgrammeMembership
table to CurriculumMembership
- TIS21-2420Getting issue details... STATUS
Duplicate ProgrammeMembership table to a new table CurriculumMembership as a exact copy
Start writing updates to both tables
Modify all the queries (downstream services included) to use new CurriculumMembership.
Monitor for a few weeks to make sure there’re no queries to old ProgrammeMembership.
Rebuild new ProgrammeMemberhsip
and populate the actual data
Drop old ProgrammeMembership table, and create a empty new table with necessary fields only.
Insert data via grouped curriculumMembership.
Update CurriculumMembership table with adding a new foreign key field
programmeMembershipUuid
and populate data for the foreign key.Save / Update in both new ProgrammeMembership and CurriculumMembership tables in parallel.
Queries
Downstream services:
NDW-ETL
The queries in NDW-ETL
- TIS21-2397Getting issue details... STATUS
TIS-Sync
- TIS21-2392Getting issue details... STATUS
Assessment
- TIS21-2422Getting issue details... STATUS
0 Comments