more meaningful report error_text when report from new template fails
Bug #2009713 reported by
Lindsay Stratton
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
When a report output fails due to some error in the template the output error_text is always something like:
DBD::Pg::st execute failed: ERROR: missing FROM-clause entry for table "3eb6b9bf3b07ee
The full message does not display, assuming there is something after "...^"?
It is cumbersome to identify the problem.
Revision history for this message
| Galen Charlton (gmc) wrote | #1 |
| Changed in evergreen: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| tags: | added: reports |
| tags: | added: ux-error-messages |
To post a comment you must log in.
I'd have to play around with DBI and DBD::Pg a bit to see if there are more options for adjust the error message - in particular, the pg_errorlevel attribute that DBD::Pg exposes looks promising - but that may be all we get. One thing that would be easy to do is append the full query that was attempted to the error text.