ClearFoundation Tracker - ClearOS
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013741ClearOSapp-reports-database - Reports Databasepublic2017-03-14 08:482017-03-14 11:58
Reporteruser2 
Assigned Touser2 
PriorityhighSeveritymajorReproducibilitysometimes
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version7.3.0 
Target Version7.3.1 UpdatesFixed in Version 
Summary0013741: MariaDB CURRENT_TIMESTAMP no longer works
DescriptionThe timestamp field for the network report is defined in the table creation:

CREATE TABLE `network` (
  ....
  `timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP,
   ...

The CURRENT_TIMESTAMP is now set to "0000-00-00 00:00:00" instead of the current time. It looks like this has been an ongoing issue according to this bug report -- https://jira.mariadb.org/browse/MDEV-6880?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel [^]

Note:
- "Resource Report" suffers from the same problem
- "Proxy Report" is unaffected. Though it does use CURRENT_TIMESTAMP, the timestamps are set explicitly based on log file timestamps.

   
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
duplicate of 0013721closed bchambers New purge script drop tables' options 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2017-03-14 08:48user2New Issue
2017-03-14 08:48user2Prioritynormal => high
2017-03-14 08:48user2Assigned To => user2
2017-03-14 08:48user2Statusnew => confirmed
2017-03-14 08:50bchambersNote Added: 0005151
2017-03-14 09:04user2Relationship addedduplicate of 0013721
2017-03-14 09:04user2Statusconfirmed => resolved
2017-03-14 09:04user2Resolutionopen => fixed
2017-03-14 11:58user2Statusresolved => closed

Notes
(0005151)
bchambers   
2017-03-14 08:50   
Is this not a duplicate/resolved issue of https://tracker.clearos.com/view.php?id=13721 [^]