Daterange filter uses invalid max timestamp for MySQL compatibility

Winter CMS Build

dev-develop

PHP Version

8.4

Database engine

MySQL/MariaDB

Plugins installed

No response

Issue description

When using the backend Filter widget for date or daterange fields, if only the start date is selected, the filter automatically fills the end date with 2999-12-31 23:59:59.
This value exceeds the maximum allowed for MySQL TIMESTAMP fields (2038-01-19 03:14:07), causing SQL errors or data truncation.

Steps to replicate

Steps to Reproduce

1. Go to any backend list with a date filter.
2. Select only the start date, leaving the end date empty.
3. Apply the filter and export or query the data.
4. The filter value for the end date will be 2999-12-31 23:59:59.

Expected Behavior

The filter should use the maximum MySQL TIMESTAMP value (2038-01-19 03:14:07) when the end date is not set, to ensure compatibility.

Actual Behavior
The filter uses 2999-12-31 23:59:59, which is not compatible with MySQL TIMESTAMP fields.

Workaround

No response

Start at the backend Filter widget's date and daterange handling, following the path used when only a start date is selected. Confirm where 2999-12-31 23:59:59 is produced, change the fallback to the stated MySQL-compatible maximum, and verify that filtering or exporting no longer causes SQL errors or data truncation.