gvSIG bugs #2591
Double fields appear always with precision 3 in tables
Status: | Closed | % Done: | 0% | |
---|---|---|---|---|
Priority: | Normal | Spent time: | - | |
Assignee: | ||||
Category: | Document table | |||
Target version: | 2.1.0-2246-testing | |||
Severity: | Critical | Add-on version: | ||
gvSIG version: | 2.1.0 | Add-on build: | ||
gvSIG build: | 2229 | Add-on resolve version: | ||
Operative System: | Add-on resolve build: | |||
Keywords: | double, float, precision, table | Proyecto: | ||
Has patch: | Hito: | |||
Add-on name: | Unknown |
Description
The double/float fields (defined in the Field Manager) appear always with precision 3 in tables, even if they're stored right. The only way to understand the "real" precision of double fields is to open the dbf file in OOo Calc actually.
Related issues
History
#1
Updated by Antonio Falciano about 10 years ago
The only way to read the precision of double fields in gvSIG (that I have forgotten to mention before) is to use the "Fields manager" when the table is in edition mode, while it's not possible in the Table properties (#2592).
The format of double fields and indirectly the precision shown in table documents seems to follow a "#,###.###" pattern (#2374) and this could lead to errors in the reading or interpretation of the cells values because of apparent truncation and rounding. Instead, a classical representation of double values is usually the best choice (#2686).
#2
Updated by Joaquín del Cerro Murciano about 10 years ago
- Severity changed from Minor to Critical
- Target version set to 2.1.0-2259-rc3
- Assignee set to Joaquín del Cerro Murciano
#3
Updated by Joaquín del Cerro Murciano about 10 years ago
- Related to gvSIG feature requests #2592: Add a precision column in the Table properties added
#4
Updated by Joaquín del Cerro Murciano about 10 years ago
- Related to gvSIG feature requests #2686: Option to skip the decimal format inherited by the current locale added
#5
Updated by Joaquín del Cerro Murciano almost 10 years ago
- Target version changed from 2.1.0-2259-rc3 to 2.1.0-2246-testing
#6
Updated by Joaquín del Cerro Murciano almost 10 years ago
- Status changed from New to Fixed
#7
Updated by Álvaro Anguix almost 10 years ago
- Status changed from Fixed to Closed