Denormalization of membership constraint.

[samchon]

erDiagram
"hub_customers" }|--o| "hub_members" : member
"hub_customers" }|--o| "hub_external_users" : external_user
"hub_customers" }|--o| "hub_citizens" : citizen
"hub_external_users" }o--o| "hub_members" : member
"hub_external_users" }o--o| "hub_citizens" : citizen
"hub_members" |o--o| "hub_citizens" : citizen
"hub_member_emails" }o--|| "hub_members" : member

Loading

Add hub_member_id to all tables in the studio that contain hub_customer_id.

All stories in our ecosystem unfold from hub_customers, which is the unit of human connection, and all entities derived from human actions also have a foreign key column called hub_customer_id. The reason they do not directly have hub_member_id is because of the normalization principle of not recording duplicate or referrable data.

However, because of this, it is difficult to create an index for "sorting", so the page-by-page query APIs may be slow. Therefore, as the first plan for backend performance tuning, we will directly record hub_member_id in the main table of the studio, slightly denormalize the tables existing in the page-by-page query APIs, and realize fast sorting through the index.

Related issue: wrtnio/main#1