0013741: MariaDB CURRENT_TIMESTAMP no longer works

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0013741

ClearOS

app-reports-database - Reports Database

public

2017-03-14 08:48

2017-03-14 11:58

Reporter

user2

Assigned To

user2

Priority

high

Severity

major

Reproducibility

sometimes

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

7.3.0

Target Version

7.3.1 Updates

Fixed in Version

Summary

0013741: MariaDB CURRENT_TIMESTAMP no longer works

Description

The 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.

Tags

No tags attached.

Attached Files

Relationships

duplicate of

0013721

closed

bchambers

New purge script drop tables' options

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

Issue History
Date Modified	Username	Field	Change
2017-03-14 08:48	user2	New Issue
2017-03-14 08:48	user2	Priority	normal => high
2017-03-14 08:48	user2	Assigned To	=> user2
2017-03-14 08:48	user2	Status	new => confirmed
2017-03-14 08:50	bchambers	Note Added: 0005151
2017-03-14 09:04	user2	Relationship added	duplicate of 0013721
2017-03-14 09:04	user2	Status	confirmed => resolved
2017-03-14 09:04	user2	Resolution	open => fixed
2017-03-14 11:58	user2	Status	resolved => closed

ClearOS Bug Tracker