connect engine discovers timestamp columns incorrectly

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