Flyspray - The bug killer!

This is the Bug Tracking System for the Flyspray project. This is not a demo!

2019-04-22: Flyspray 1.0-rc9 released See

ID Category Task Type Severity  desc Summary Status Progress Assigned To Due In Version Opened Last Edited
 1764 Backend/CoreBug ReportLow PostgreSQL: No activity graphs displayed Closed
Jouni Ahto1.0113.08.201222.04.2015 Task Description

Instead of a activity graph, some broken images are displayed. After minimal investigation I found following error:

Query {SELECT count(date(from_unixtime(event_date))) as val FROM "flyspray_history" h left join "flyspray_tasks" t on t.task_id = h.task_id WHERE t.project_id = ? AND date(from_unixtime(event_date)) = str_to_date(?, '%m/%d/%Y')} with params {4,08/12/2012} Failed! (FEHLER: Funktion from_unixtime(integer) existiert nicht LINE 1: SELECT count(date(from_unixtime(event_date))) as val ^ HINT: Keine Funktion stimmt mit dem angegebenen Namen und den Argumenttypen überein. Sie müssen möglicherweise ausdrückliche Typumwandlungen hinzufügen.)

which points to a missing function "from_unixtime" in PostgreSQL and it is true, it's a mysql specific function. One can build this function on PostgreSQL. stephe did it:!topic/flyspray/_VigAhVd-CU. If ever possible don't use these specific functions or this will break all database compatibilities with other than mysql

 1591 Backend/CoreBug ReportLow PostgreSQL Advanced Search is Case-Sensitive; MySQL is  ...Closed
Jouni Ahto1.0203.08.200919.03.2015 Task Description

I apologize if this is a duplicate... I did search pretty hard for another filing.

Text searches are case-sensitive on PostgreSQL where they aren't on MySQL (I'm guessing MySQL is the desired behavior). When checking the code, it has to do with the use of the 'LIKE' keyword: it's case-insensitive on MySQL and case-sensitive on PostgreSQL.

I fixed it for my own uses by changing it to ILIKE instead (PostgreSQL-only), but a more generic approach would be more appropriate for Flyspray Proper. The Right Way To Fix This™ probably involves a change to ADOdb to allow for an abstraction of the LIKE keyword depending on the database in use. The Mostly-Right Way To Fix This would be to use something generic across MySQL and PostgreSQL like UPPER() or something to compare the data.

Showing tasks 51 - 52 of 52 Page 2 of 2

Available keyboard shortcuts


Task Details

Task Editing