Project

General

Profile

Actions

Bug #4089

closed

A query about execution date of reports still use old parameters

Added by Vincent MEMBRÉ over 10 years ago. Updated over 10 years ago.

Status:
Released
Priority:
1
Category:
Web - Compliance & node report
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When the function to get execution date of nodes from the database is called there is an error launched:

bad SQL grammar [select distinct date from reportsexecution where nodeId = ? and date
 >= ? and executiontimestamp < ? order by executiontimestamp ]; nested exception is org.postgresql.util.PSQLExceptio
n: ERREUR: la colonne ? executiontimestamp ? n'existe pas

the column executiontimestamp does not exists in the new reportsExecution table (#3945]

change executionTimestamp to date repair the query

Actions #1

Updated by Vincent MEMBRÉ over 10 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/351
Actions #2

Updated by François ARMAND over 10 years ago

  • Assignee changed from François ARMAND to Nicolas CHARLES

I believe Nicolas will be better up to validate that one.

Actions #3

Updated by Vincent MEMBRÉ over 10 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #5

Updated by Vincent MEMBRÉ over 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.8.0~rc1, which was released on Friday 25/10/2013.
Check out:

Actions

Also available in: Atom PDF