Different result from Mysql when casting a type conversation from a long string to an integer.

[SunRunAway]

Bug Report

Please answer these questions before submitting your issue. Thanks!
Type conversation from a long string to integer.

1. What did you do?
   If possible, provide a recipe for reproducing the error.

SELECT '415290769594460e2e485922904f345d' ^ 1;
SELECT cast('415290769594460e2e485922904f345d' as UNSIGNED);

2. What did you expect to see?

In MySQL,

mysql> SELECT '415290769594460e2e485922904f345d' ^ 1;
+----------------------------------------+
| '415290769594460e2e485922904f345d' ^ 1 |
+----------------------------------------+
|                        415290769594461 |
+----------------------------------------+
1 row in set, 1 warning (0.00 sec)

mysql> SELECT cast('415290769594460e2e485922904f345d' as UNSIGNED);
+------------------------------------------------------+
| cast('415290769594460e2e485922904f345d' as UNSIGNED) |
+------------------------------------------------------+
|                                      415290769594460 |
+------------------------------------------------------+
1 row in set, 1 warning (0.00 sec)

3. What did you see instead?

In TiDB,

mysql> SELECT '415290769594460e2e485922904f345d' ^ 1;
+----------------------------------------+
| '415290769594460e2e485922904f345d' ^ 1 |
+----------------------------------------+
|                      41529076959446001 |
+----------------------------------------+
1 row in set, 1 warning (0.00 sec)

mysql> SELECT cast('415290769594460e2e485922904f345d' as UNSIGNED);
+------------------------------------------------------+
| cast('415290769594460e2e485922904f345d' as UNSIGNED) |
+------------------------------------------------------+
|                                    41529076959446000 |
+------------------------------------------------------+
1 row in set, 1 warning (0.00 sec)

4. What version of TiDB are you using (tidb-server -V or run select tidb_version(); on TiDB)?
   fdbc149

[zz-jason]

close due to fixed