Maybe the person load helper can do this. Most code in this situation uses the model which claims to provide a sane list already.
I do not think the proper fix is more guards in the code. there are 10,000 (bug, blueprint, question, ...) subscription belonging to merged-deactivated persons. We query them ever few minutes or less. Our send mail code is dropping email to them at the last minute. This data does not belong in the database. As I proposed in another bug, we could use a garbo job to purge the many forms of subscription. We can have a grace period for a few days so for deactivated/suspended users so that nothing is lot of the account is reinstated.
Maybe the person load helper can do this. Most code in this situation uses the model which claims to provide a sane list already.
I do not think the proper fix is more guards in the code. there are 10,000 (bug, blueprint, question, ...) subscription belonging to merged-deactivated persons. We query them ever few minutes or less. Our send mail code is dropping email to them at the last minute. This data does not belong in the database. As I proposed in another bug, we could use a garbo job to purge the many forms of subscription. We can have a grace period for a few days so for deactivated/ suspended users so that nothing is lot of the account is reinstated.