This would be similar to the Filter object and relatives, with a mutable variant, and a variant for database entries. The main problem here is that the abuse_filter_log table is basically never queried alone. At minimum, we JOIN it with abuse_filter to determine whether a filter is hidden, so either we store this information somewhere (but then the lack separation of concerns would be worsened), or we'd need two distinct queries (not good performance-wise).