Bug #71285 Support updates of NON NULL DEFAULT timestamp columns through memcached

• Submitted: 3 Jan 2014 7:42
• Reporter: Erlend Dahl
• Status: Verified
• Category: MySQL Server: Memcached
• Severity: S4 (Feature request)
• Version: 5.6+
• OS: Any
• CPU Architecture: Any

[3 Jan 2014 7:42] Erlend Dahl

Description:
In bug#68974 it was reported that having NOT NULL columns in an InnoDB
table used by the Memcached plugin would prevent memcached from
setting new key/value pairs. The issue was addressed in the
troubleshooting section of the InnoDB memcached documentation.

However, this does not cover the use case where timestamp columns are
used for telling when records were created and/or updated, e.g.

CREATE TABLE `memstash` (
  `k` varchar(255) NOT NULL,
  `v` longtext,
  `flags` int(11) DEFAULT NULL,
  `cas_column` bigint(20) unsigned DEFAULT NULL,
  `expires` int(10) unsigned DEFAULT NULL,
  `date_created` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `date_updated` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  PRIMARY KEY (`k`),
  KEY `v` (`v`(255))
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

How to repeat:
See above.

Suggested fix:
Feature request for the InnoDB memcached plugin.