Expiry date field overflows – convert to BIGINT for Y2038 compatibility

Problem/Motivation

In the current version of Acquia DAM, the acquia_dam_expiry_date_value field in the media__acquia_dam_expiry_date table (and its revision tables) is defined as INT (32-bit).

This causes numeric overflow errors when storing expiry dates beyond 2038 (Unix timestamp > 2,147,483,647), resulting in:

Queue processing failures

Media save errors

SQLSTATE[22003]: Numeric value out of range

The goal is to make the expiry date column Y2038-compatible and safe for high timestamps.

Steps to reproduce

Install Acquia DAM on Drupal 10.

Create or import a media item with an expiry date beyond 2038 (e.g., timestamp 2376104400).

Process the DAM sync queue or save the media item.

Observe the SQL overflow error:

SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column 'acquia_dam_expiry_date_value'

Proposed resolution

Convert all relevant expiry date columns from INT → BIGINT (64-bit) in:

media__acquia_dam_expiry_date

media_revision__acquia_dam_expiry_date

media_field_revision__acquia_dam_expiry_date

Add a helper function to perform the alteration.

Apply the fix in both:

hook_install() → fresh installs

hook_update_N() → existing sites

Ensure compatibility with Drupal 10 and Acquia DAM latest version.

Remaining tasks

Review and test patch on local, staging, and production environments.

Confirm queue items with future expiry dates work correctly.

Verify no data loss occurs during the column type conversion.

User interface changes

None. This is a database-level fix only.

API changes

None. Existing APIs for media entities remain compatible.

Only internal storage column type changes.

Data model changes

acquia_dam_expiry_date_value column in all DAM-related tables is changed from INT → BIGINT.

Affects:

media__acquia_dam_expiry_date

media_revision__acquia_dam_expiry_date

media_field_revision__acquia_dam_expiry_da