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

connect engine discovers timestamp columns incorrectly

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.0.7
    • 10.0.8
    • None

    Description

      Timestamp columns in the CONNECT engine are discovered incorrectly: connect.mysql_new test fails as

      -  `d` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
      +  `d` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,

      Looking at the result file, one can see that the original MyISAM table had

        `d` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,

      So this column used to be discovered correctly for the CONNECT table, but now it is not.

      Suspected changeset is revid:bertrandop@gmail.com-20131203215940-ouk00oy06fsl011v (Add support for unsigned numeric types).

      Attachments

        Activity

          People

            bar Alexander Barkov
            serg Sergei Golubchik
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.