Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.0.7
-
Fix Version/s: 10.0.8
-
Component/s: None
-
Labels:
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).
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
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