[MDEV-5469] connect engine discovers timestamp columns incorrectly Created: 2013-12-18  Updated: 2014-01-14  Resolved: 2014-01-14

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.7
Fix Version/s: 10.0.8

Type: Bug Priority: Major
Reporter: Sergei Golubchik Assignee: Alexander Barkov
Resolution: Fixed Votes: 0
Labels: connect-engine


 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).

 Comments   
Comment by Alexander Barkov [ 2014-01-14 ]

Fixed in 10.0 with this revision:

revno: 3913.1.20
committer: Olivier Bertrand <bertrandop@gmail.com>
branch nick: 10.0-connect
timestamp: Thu 2013-12-19 12:56:06 +0100
message: Add extra column info in discovery

Generated at Thu Feb 08 07:04:37 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.