Bug #86019 explicit_defaults_for_timestamp and timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP
Submitted: 20 Apr 2017 11:44 Modified: 14 Jun 2017 13:35
Reporter: Søren Thing Andersen Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.6.35 OS:Any
Assigned to: CPU Architecture:Any

Contributions can be accepted to Open bugs only.