Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-4872

Inserting a huge number into a TIME column produces a wrong result

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.0.3, 5.5.32, 5.3.12
    • Fix Version/s: 5.3.13, 10.0, 5.5
    • Component/s: None
    • Labels:
      None

      Description

      MariaDB [test]> DROP TABLE IF EXISTS t1; CREATE TABLE t1 (a TIME); INSERT INTO t1 VALUES (100000000000000000); SHOW WARNINGS; SELECT * FROM t1;
      Query OK, 0 rows affected (0.00 sec)
      
      Query OK, 0 rows affected (0.07 sec)
      
      Query OK, 1 row affected, 1 warning (0.00 sec)
      
      +---------+------+----------------------------------------+
      | Level   | Code | Message                                |
      +---------+------+----------------------------------------+
      | Warning | 1265 | Data truncated for column 'a' at row 1 |
      +---------+------+----------------------------------------+
      1 row in set (0.00 sec)
      
      +----------+
      | a        |
      +----------+
      | 00:00:00 |
      +----------+
      1 row in set (0.00 sec)
      

      The expected result is 'maximum possible value', which is '838:59:59'.

      MySQL 5.5 and 5.6 correctly insert the maximum possible value.

        Gliffy Diagrams

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              bar Alexander Barkov
              Reporter:
              bar Alexander Barkov
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: