Wrong results for a huge unsigned value inserted into a TIME column

Description

The expected error text is:

MySQL-5.6 is not affected.

When running in a non-traditional mode, the same huge unsigned value
produces a negative value in the column:

returns

The expected result is the maximum positive number.

Comparision of TIME to a huge unsigned number also returns a wrong result:

The expected result is 0.

A similar problem is observed with dynamic columns:

The result for t2 should be '-838:59:59', and a warning for both t1 and t2 should be displayed.

Environment

None

Status

Assignee

Alexander Barkov

Reporter

Alexander Barkov

Labels

External issue ID

None

External issue ID

None

Fix versions

Affects versions

Priority

Major
Configure