DataTables serverSide: true – inconsistent pagination after schema change

Goal

Maintain correct pagination and record counts when the underlying database schema is altered (e.g., adding a column, changing a column type) while using DataTables with serverSide: true.

Current Uncertainty

DataTables expects the server to return recordsTotal and recordsFiltered values that match the result set for the requested start and length parameters. A schema change can silently affect the SQL query (e.g., new indexes, altered column types) and lead to mismatched counts, causing the UI to display an incorrect number of pages or truncated data. The plugin does not provide built‑in validation of these values, and there is no documented rollback‑safe mechanism to detect or correct such mismatches.

Questions

1. What server‑side checks should be added to verify that recordsTotal and recordsFiltered accurately reflect the current schema state before sending the response?
2. Is there a recommended DataTables configuration or extension that can automatically detect and warn about mismatched pagination counts after a schema change?
3. How can we design a rollback strategy that ensures the client’s pagination UI remains consistent if the server schema is reverted mid‑session?