Defect #15944
Some columns in redmine should be double data type, i.e estimated_hours
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Database | |||
| Target version: | - | |||
| Resolution: | Affected version: | 2.3.3 |
Description
Dear Team,
We have some problems with fields having float data type (mysql db), sometimes query is wrong.
Example:
We have an issue with estimated_hours = 1.6, when we filter in issue list with parameters:
- estimated_hours >=/is 1.6: the result is right.
- estimated_hours <= 1.6: the list doesn't contain that issue
I viewed source code, the team handled it by adding a range, but I don't think it resolve this problem.
Hope team fix it both in database and source code.
History
#1
Updated by Daniel Felix over 8 years ago
Yes, I encountered the same problems in small edge cases. Float isn't a good datatype for precission. It's just a bit faster and sometimes a bit smaller in spaceconsumption (compared to some other datatypes).
I don't find the correct issue, but in the tracker is another one open, which aims to the same problem.