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

CONNECT engine loses microseconds in timestamps

Details

    Description

      CONNECT engine truncates microseconds in TIMESTAMP/DATETIME values upon storing them:

      MariaDB [test]> create table tc (t timestamp(6)) engine=CONNECT table_type=DOS file_name='tc.file';
      Query OK, 0 rows affected (0.03 sec)
       
      MariaDB [test]> insert into tc values ('2012-12-12 12:12:12.123456');
      Query OK, 1 row affected (0.01 sec)
       
      MariaDB [test]> select * from tc;
      +----------------------------+
      | t                          |
      +----------------------------+
      | 2012-12-12 12:12:12.000000 |
      +----------------------------+
      1 row in set (0.00 sec)
      

      $ cat data/test/tc.file
       1355307132
      

      As a side-effect, system versioning for CONNECT tables does not work at all.

      Attachments

        Activity

          elenst Elena Stepanova created issue -
          elenst Elena Stepanova made changes -
          Field Original Value New Value
          Assignee Olivier Bertrand [ bertrandop ]
          bertrandop Olivier Bertrand made changes -
          issue.field.resolutiondate 2018-04-22 17:54:52.0 2018-04-22 17:54:52.071
          bertrandop Olivier Bertrand made changes -
          Fix Version/s N/A [ 14700 ]
          Fix Version/s 10.3 [ 22126 ]
          Resolution Not a Bug [ 6 ]
          Status Open [ 1 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 86706 ] MariaDB v4 [ 154216 ]

          People

            bertrandop Olivier Bertrand
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.