Defect #13667
Internal error on custum queries after Upgrade 2.2 -> 2.3 (defect column_names)
Status: | Closed | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Issues | |||
Target version: | - | |||
Resolution: | Invalid | Affected version: | 2.3.0 |
Description
After upgrading redmine from 2.2 to 2.3 I get a internal error on custom queries.
I adapted the column column_names
from table queries
as follows to fix this bug:
- --- !!null
- ...
+ ---
This issue is similar to #13617.
Related issues
History
#1
Updated by Filou Centrinov about 9 years ago
For me Redmine 2.3 stores
--- ...but is also satisfied with
--- !!null ...
and also
---
rake about:
Ruby version 1.9.3 (i386-mingw32) RubyGems version 2.0.2 Rack version 1.4 Rails version 3.2.13
#2
Updated by Marius BALTEANU over 3 years ago
- Status changed from New to Closed
- Resolution set to Invalid
If someone still has this problem, it can find in this ticket or in #13617 how to fix the problem.