Comment 4 for bug 1496522

Glad to have more eyes on it! LOL typos. I like your query improvement. Can the invalid events be mitigated with a clever event definition? The delay default is set to last_payment_ts. Maybe there is something we can do there? I'm not sure exactly what. Perhaps the query could include a date that the trigger could compare to. I assume we want this notice to repeat even when the patron touched their account more than 30 days ago?