Good to hear! Thanks for investigating. Downgraded the priority of this as a result. I actually reported this as the outcome of a summit conversation with Adam Young- neither of us were aware that they were already being purged.
I guess that presents another potential issue, though. If DELETEs are being emitted on every list_events(), does that cause a negative performance impact or unnecessary load on the database? The benefit of the current implementation, I assume, is that the controller is far less likely to emit expired events. Events are intended to be relatively rare, though, so incredibly frequent DELETEs should be unnecessary.
Good to hear! Thanks for investigating. Downgraded the priority of this as a result. I actually reported this as the outcome of a summit conversation with Adam Young- neither of us were aware that they were already being purged.
I guess that presents another potential issue, though. If DELETEs are being emitted on every list_events(), does that cause a negative performance impact or unnecessary load on the database? The benefit of the current implementation, I assume, is that the controller is far less likely to emit expired events. Events are intended to be relatively rare, though, so incredibly frequent DELETEs should be unnecessary.