Totally wrong approach.
The database is concurrent at the moment of each action. What you are suggesting is againste every rule of the relational database concept. It's not the program's fault if you changed something and then remove the warning. Remove the warning first and then make changes at the warning type.
If I follow your idea, I should also store the number of days a member was banned, who long each warning is active (maturity period) etc. Dead end.
Sorry!
|