Bug #6038: Wrong reporting after execution of migration script to change the way reports are used from the database - Rudder - Issue Tracker

Actions

Copy link

Bug #6038

closed

Wrong reporting after execution of migration script to change the way reports are used from the database

Added by Nicolas CHARLES over 9 years ago. Updated over 9 years ago.

Status:

Released

Priority:

N/A

Assignee:

François ARMAND

Category:

Web - Compliance & node report

Target version:

3.0.0~rc1

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

in #6005, we changed the way we handle the reporting, by taking the most recent one (insertion wise) from the database.
however, we left a lot of entry to null; which is not good because when we sort, NULL is always before the others (DESC or ASC wise)
We need to have a default value to 0 to correct this

Note: the problems corrects itself after a while, when old reports are deleted from the database

Related issues 1 (0 open — 1 closed)