Bug #109941 wrong result of timestampadd

Description:
timestampadd(month,1,date '2024-03-30') and select timestampadd(month,1,date '2024-03-31') get the same result.

mysql>  select timestampadd(month,1,date '2024-03-30');
+-----------------------------------------+
| timestampadd(month,1,date '2024-03-30') |
+-----------------------------------------+
| 2024-04-30                              |
+-----------------------------------------+
1 row in set (0.00 sec)

mysql>  select timestampadd(month,1,date '2024-03-31');
+-----------------------------------------+
| timestampadd(month,1,date '2024-03-31') |
+-----------------------------------------+
| 2024-04-30                              |
+-----------------------------------------+
1 row in set (0.00 sec)

How to repeat:
As the description shows.

Suggested fix:
mysql>  select timestampadd(month,1,date '2024-03-30');
+-----------------------------------------+
| timestampadd(month,1,date '2024-03-30') |
+-----------------------------------------+
| 2024-04-30                              |
+-----------------------------------------+
1 row in set (0.00 sec)

tidb> select timestampadd(month,1,date '2024-03-31');
+-----------------------------------------+
| timestampadd(month,1,date '2024-03-31') |
+-----------------------------------------+
| 2024-05-01                              |
+-----------------------------------------+
1 row in set (0.00 sec)

Hello Huaiyu Xu,

Thank you for the report and test case.

regards,
Umesh

This is expected behaviour. Per Development, "...[W]hen
a month interval is added to a date or datetime value:
When the resulting date ends on a day that does not exist
in the respective month, the day is adjusted to be the last
day of the month."

Note that DATE_ADD() behaves in the same fashion.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly.

Fixed in mysqldoc rev 74951. Closed.