Bug 130190 - Number of decimals isn't taken into account in Base, when viewing table values
Summary: Number of decimals isn't taken into account in Base, when viewing table values
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.3.3.2 release
Hardware: All Linux (All)
: medium trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-25 09:41 UTC by nhk1994
Modified: 2024-03-14 03:16 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
this is a video of problem (7.64 MB, video/mp4)
2020-02-06 16:15 UTC, nhk1994
Details

Note You need to log in before you can comment on or make changes to this bug.
Description nhk1994 2020-01-25 09:41:34 UTC
Description:
in libre office base i create a field and choose field type ass "decimal" up to 4 decimal places when i try to input 1.001 its give value only 1 ,if i input 1.101 its give 1 
but when i entered 1.01 its give 1.01 correct 
please solve it 
thank you

Steps to Reproduce:
1.create a table in libre office base
2.take any fild as decimal up to more than 3 or 4 decimal places.
3.enter value as 1.0001 or 1.101

Actual Results:
1

Expected Results:
1.0001 or 1.101


Reproducible: Always


User Profile Reset: No



Additional Info:
the value auto change it self we can't enter value  as we want...
thank you
Comment 1 Alex Thurgood 2020-01-29 11:33:50 UTC
@nhk1994 : please specify which kind of database engine you are using :

- default embedded hsqldb 1.8.0
- embedded firebird
- some other db backend
- if a different db backend than the the embedded engines, which driver and version of driver are you using ?

Setting NEEDINFO
Comment 2 Robert Großkopf 2020-01-29 16:39:04 UTC
Tested it with embedded Firebird database. Added a field for Decimal with 4 decimal places. Opened the table for input values. Added '1.0001' to this field. Works as expected.

Tested with LO 6.3.4.2 on OpenSUSE 15.1 64bit rpm Linux.
Comment 3 nhk1994 2020-02-06 16:15:27 UTC
Created attachment 157703 [details]
this is a video of problem
Comment 4 QA Administrators 2020-02-09 03:43:26 UTC Comment hidden (obsolete)
Comment 5 Julien Nabet 2020-03-13 22:01:12 UTC
On pc Debian x86-64 with master sources updated today, I could reproduce this kind of behaviour.
Indeed, whatever embedded Firebird or embedded HSQLDB, if I put 4 decimals, I can put (EnUS UI but French decimal so ","):
1
1,1
1,11
but 1,111 is changed into 1,11
Comment 6 QA Administrators 2022-03-14 03:34:28 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2024-03-14 03:16:12 UTC
Dear nhk1994,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug