Exactly. Every time there’s a change in the autorun containing the fetch.
Changes listed from aldeed’s comments:
// * DataTables reran ajax due to sort changing. // * DataTables reran ajax due to page changing. // * DataTables reran ajax due to results-per-page changing. // * DataTables reran ajax due to search terms changing. // *selector
attribute changed reactively // * Docs were added/changed/removed by this user or // another user, causing visible result set to change.
So each time that happens DT will call back to Tabular to create new blaze views for each row. So we delete the old ones before it. There might be some way to be a bit cleverer here and reuse them but I don’t think it’s trivial.