[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[savannah-help-public] [sr #109536] Trouble Using Savannah Bug Tracker
From: |
Jean Delvare |
Subject: |
[savannah-help-public] [sr #109536] Trouble Using Savannah Bug Tracker |
Date: |
Thu, 4 Oct 2018 04:48:08 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 |
Follow-up Comment #8, sr #109536 (project administration):
Same problem here on another project (quilt):
_db_query: SQL query error Unknown column 'bugs.bug_id' in 'on clause' in
[SELECT count(DISTINCT bugs.bug_id) AS count FROM bugs ,user user_assigned_to
LEFT JOIN bugs_history ON ((bugs_history.bug_id = bugs.bug_id ) AND
(bugs_history.date >= 0) AND (bugs_history.field_name = NULL)) WHERE
bugs.group_id='3520' AND (bugs.spamscore < '5' OR submitted_by='12366') AND
user_assigned_to.user_id=bugs.assigned_to AND bugs_history.bug_id IS NULL]_
I think it is caused by previous search criteria which are remembered but no
longer valid. Using "Bugs > Reset to open" as advised by Armin works around
the problem (thanks Armin!) However it is not exactly user-friendly.
Ideally, the old query should be transparently converted to the equivalent
query for the new model. If that is not possible or is considered too much
work for a transitory issue, then invalid queries should be automatically
forgotten. In other words, when a query fails, instead of spitting the
database error in the browser, you should redirect to the same page as "Bugs >
Reset to open".
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?109536>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [savannah-help-public] [sr #109536] Trouble Using Savannah Bug Tracker,
Jean Delvare <=