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

Microseconds: Precision is ignored in CURRENT_TIMESTAMP(N) when it is given as a default column value

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.0.0, 5.5.25, 5.3.7
    • Fix Version/s: 10.0.1, 5.5.29, 5.3.10
    • Component/s: None
    • Labels:
      None

      Description

      CREATE TABLE t (a TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(0));
      # Query OK, 0 rows affected (0.20 sec)
       
      INSERT INTO t VALUES (NULL);
      # Query OK, 1 row affected (0.04 sec)
       
      SELECT * FROM t;
      # +-------------------------+
      # | a                       |
      # +-------------------------+
      # | 2012-08-07 04:18:48.353 |
      # +-------------------------+
      # 1 row in set (0.00 sec)

      Inserting CURRENT_TIMESTAMP(0) explicitly works as expected:

      INSERT INTO t VALUES (CURRENT_TIMESTAMP(0));
      # Query OK, 1 row affected (0.04 sec)
       
      SELECT * FROM t;
      # +-------------------------+
      # | a                       |
      # +-------------------------+
      # | 2012-08-07 04:18:48.353 |
      # | 2012-08-07 04:23:51.000 |
      # +-------------------------+
      # 2 rows in set (0.01 sec)

        Attachments

          Activity

            People

            • Assignee:
              serg Sergei Golubchik
              Reporter:
              elenst Elena Stepanova
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: