We should implement some kind of automatic garbage collection for the throttles, password_resets, and verifications tables. This could be similar to the way session gc works, so that records are checked for removal whenever the table is next written to.
In some applications, it might be desirable to run garbage collection on the activities table as well. Obviously, this should all be configurable.
We should implement some kind of automatic garbage collection for the
throttles,password_resets, andverificationstables. This could be similar to the way session gc works, so that records are checked for removal whenever the table is next written to.In some applications, it might be desirable to run garbage collection on the
activitiestable as well. Obviously, this should all be configurable.