CodePudding user response:
Design a tag, look to whether can after each consumption upgradingCodePudding user response:
This and MFC without a dime relationship, this is a question of user management strategyCodePudding user response:
This is the membership card billing system course design requirements doCodePudding user response:
With MFC it doesn't matter, the level of members with that score, 0-1000 to regular members, more than 1000 for the VIP, each time to update the score line, display level and query classification score, discount is, how many points in the specified strategies to itCodePudding user response:
The database for each user increases the levels of a field tag, it has nothing to do with MFC, is the business logic problemCodePudding user response:
directly in the database, there are two ranks and the current consumption amount fields don't have to do isCodePudding user response:
MFC? What is the relationship between the MFC?CodePudding user response:
MFC=didn't eat riceCodePudding user response:
Estimates are you MFC + access database architecture, it is recommended that the user level indicator on the database, finish every time consumption, recalculate the user level,CodePudding user response:
Data set a flag, after each consumer, if the logo was detected, then the discount several, otherwise the cumulative total consumption amount, if the amount is at or above the threshold, set this flag;