DataTables Server-Side Pagination Rollback After Column Addition in v1.13.x

Problem Statement

DataTables server-side processing relies on an initial AJAX request to populate recordsTotal and recordsFiltered values that drive pagination controls. When the underlying database schema changes—such as adding or removing columns—the stored pagination state may reference column configurations that no longer exist or have different positions.

Affected Feature

The server-side pagination feature in DataTables versions 1.13.x lacks an automatic mechanism to detect schema modifications and reset the internal state accordingly. This creates a boundary condition where users navigating through pages after a structural database change may encounter mismatched row counts or missing data references.

Constraints and Uncertainty

The current implementation does not provide a built-in event or callback that signals schema incompatibility. Manual intervention through page reload or state reset is required. The behavior specifically manifests when using server-side processing mode with AJAX data sources, where the initial recordsTotal response becomes stale after column modifications.

Specific Questions

• Does DataTables expose any event or configuration option to automatically trigger state reset when column definitions change between requests?
• What is the recommended pattern for handling pagination state recovery when the server-side data structure has been modified without user-initiated page refresh?
• How should developers configure their servers to signal schema changes to DataTables clients to prevent stale pagination references?