在部署程序時遇到的一個問題，MySQL定義舉例如下：
復(fù)制代碼 代碼如下:
CREATE TABLE `example` (
`id` INTEGER UNSIGNED NOT NULL AUTO_INCREMENT,
`created` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
`lastUpdated` TIMESTAMP NOT NULL ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (`id`)
) ENGINE=InnoDB;
這段SQL是我從項目中摘取出來的，在測試機(jī)器上一切正常，但是部署到生產(chǎn)機(jī)器上MySQL報錯：
復(fù)制代碼 代碼如下:
ERROR 1293 (HY000): Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause.
意思是只能有一個帶CURRENT_TIMESTAMP的timestamp列存在，但是為什么本地測試卻沒有任何問題呢，本地測試的機(jī)器安裝的MySQL版本5.6.13，而生產(chǎn)機(jī)器上安裝的卻是5.5版本，搜索網(wǎng)絡(luò)后得知這兩種版本之間對于timestamp處理的區(qū)別在于：
在MySQL 5.5文檔有這么一段話：
復(fù)制代碼 代碼如下:
One TIMESTAMP column in a table can have the current timestamp as the default value for initializing the column, as the auto-update value, or both. It is not possible to have the current timestamp be the default value for one column and the auto-update value for another column.
而在MySQL 5.6.5做出了以下改變：
復(fù)制代碼 代碼如下:
Previously, at most one TIMESTAMP column per table could be automatically initialized or updated to the current date and time. This restriction has been lifted. Any TIMESTAMP column definition can have any combination of DEFAULT CURRENT_TIMESTAMP and ON UPDATE CURRENT_TIMESTAMP clauses. In addition, these clauses now can be used with DATETIME column definitions. For more information, see Automatic Initialization and Updating for TIMESTAMP and DATETIME.
根據(jù)網(wǎng)上的解決方案，可以使用觸發(fā)器來替代一下：
復(fù)制代碼 代碼如下:
CREATE TABLE `example` (
`id` INTEGER UNSIGNED NOT NULL AUTO_INCREMENT,
`created` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
`lastUpdated` DATETIME NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB;
DROP TRIGGER IF EXISTS `update_example_trigger`;
DELIMITER //
CREATE TRIGGER `update_example_trigger` BEFORE UPDATE ON `example`
FOR EACH ROW SET NEW.`lastUpdated` = NOW()
//
DELIMITER ;
