DataTables destroy method leaves stale state after upgrade rollback
DataTables destroy method and state persistence When a DataTable instance is destroyed with the destroy() method, the library removes its internal bookkeeping but leaves the underlying DOM elements, event handlers, and any persisted state untouched. This behavior becomes problematic during a failed upgrade: the new version may initialize over the old table,
datatables