Level 122
If you need to retain previous renewal information then, yes, your table will grow large.
If you dont need to retain it then just have a scheduler job to remove older entries.
Sep 7, 2018
1
Level 3
How to design table for tracking member reissue/renewal date logs?
So, you have a member who register on 2018-09-01 and has a expiry date on 2018-09-30. On 2018-09-30, the account expired and the customer comeback to pay for a renewal. The goal is I want to have a table for keep tracking the reissue date. If I were to have a reissue_logs table that has column user_id, reissue_date_time, price_paid, ... then this table could easily go over millions record after a years.
I'm sure this kind of thing has done by many and I want to see how you design this. Thank
Please or to participate in this conversation.