Issue 59516 - IT: Cannot insert decimal, real or float values properly
Summary: IT: Cannot insert decimal, real or float values properly
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0
Hardware: PC All
: P3 Trivial with 10 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2005-12-18 22:19 UTC by Andrea Pescetti
Modified: 2013-02-07 22:35 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Andrea Pescetti 2005-12-18 22:19:07 UTC
Verified in OOo 2.0.1-RC5-IT, may affect other locales.

1. Open Base and create a new database.
2. Create a table with three fields: "decimal" of type decimal, "float" of type
float, "real" of type real. Add an auto-incrementing primary key when prompted.
3. Double click on the table to insert data.
4. Select a (comma-separated, as per locale) numeric format with two decimals
right-clicking on each column heading.
5. Type "2.22" in all columns and move to the next record.
6. Data are changed into "0,0000", "2.22", "0,1" respectively.
7. Type "2,22" (decimal separator is a comma in IT) in all columns and move to
the next record.
8. Data are changed into "2,0000", "2", "2,22" respectively.

Something is not working because, at the very least, REAL and FLOAT should be
identical as per HSQLDB documentation:

[Reported by Filippo Cerulo during Italian QA tests]
Comment 1 alanzagh 2006-01-07 12:59:17 UTC
confermo i risultati:
0,00 - 2.22 - 0,10
2,00 - 2 - 2,22
uso microsoft windows xp - home edition - versione 2002 .  service pack 2
Comment 2 mariogovoni 2006-01-10 10:29:19 UTC
*** Issue 59516 has been confirmed by votes. ***
Comment 3 christoph.lukasiak 2006-06-12 15:12:45 UTC
does it still occure in current version

Comment 4 Andrea Pescetti 2006-06-12 16:20:24 UTC
Yes, I confirm this same behavior in OOo 2.0.3-RC5 Italian.

The only difference: "0,0000" and "2,0000" are now formatted as "0,00" and "2,00".
Comment 5 christoph.lukasiak 2006-08-21 15:30:06 UTC
clu->pescetti: 1. due to the fact, that your settings define a comma seperated
handling, the insert of a '.' is in this case an 'unknown' sign (if no thousands
seperator is defined) => from my point of view this is rather a needful feature
enhancement for the number formatter  .. somtimes '.' seperated numbers are
interpreted as date numbers and after that formated again .. ugly handling :( i
send this as feature enhancement to the requirements team
2. the ',' - part is a little bit different: if you open the table definition of
the used table and travel the decimal and the float field, you can see in the
below 'field property' area, that the float field has 0 decimal places, so even
if you change the 'display' format in two decimal places, this field cannot
handle that (an info message could clarify that) - the decimal field should
work, after you change the decimal places in 2 and save

change in 'feature enhancement' and send further to the requirements team
Comment 6 ace_dent 2008-05-15 15:23:51 UTC
This Issue requires more information ('needmoreinfo'), but has not been updated
within the last year. Please re-test with one of the latest versions of OOo -
the problem(s) may have already been addressed. Either use the recent stable
or consider trying the new OOo 3 BETA (still in testing):
Please report back the outcome so this Issue may be closed or progressed as
necessary - otherwise it may be Resolved as Invalid in the future. You may also
wish to search for (and note) any duplicates of this Issue that may have
advanced further :
Many thanks,
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~
Comment 7 Andrea Pescetti 2008-05-17 15:06:36 UTC
The issue was assigned to requirements by clu, so there is no more info to add.
Removing "needmoreinfo".