removing warnings

[Tom1234]

If you issue a warning and then change the default points associated with that warning type and then try to totally remove the warning from the user's account, it deducts the current point value rather than the point value at the time of the warning issuance.

This resulted in issuing a warning for 10 points, but then removing the warning only removed 5 points, leaving 5 points on the account yet no warnings. I had to go into the DB to change the value of warning level points to 0.

I believe you should store the point value at warn time with the warning. Then deduct that amount of points if it is removed, rather than the current point value for that warning type.

[sv1cec]

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!