Description: I have a split HSQLDB version 2.3.2, with embedded or split HSQLDB version 1.8 there was no bug. When a table or view is used in Calc, a decimal field (length 4, decimal places 2, format example 0,00) is formatted as currency. Even if manually formatted as 0,00 in Calc, after Data →Refresh Range, the currency symbol is there again. This is very annoying, because I use the column to store weights. This behavior occurs not in Writer. I'll attach an example database and Writer and Calc documents. The bug still exists in 6.4.2.2, I already experienced it in 6.0.7. I don't know, what the earliest affected version is. Steps to Reproduce: 1. Create a split database with HSQLDB 2.3.2. Create a table with a column with field type Decimal, lenght 4, decimal places 2. The format example shows 0,00 € then, so change it to 0,00. 2. Fill in some values. 3. Register the database and import the table in Calc via View -> Data Sources -> Select the database -> select the table -> Data to Text Actual Results: The table is imported but the format of the decimal column is a currency format. (With my German Locale it's #.##0,00 [$€-407];[ROT]-#.##0,00 [$€-407] ) Even if I manually format the column as 0,00 in Calc, after Data →Refresh Range is clicked, the currency symbol is there again. Expected Results: The data is correctly imported with it's format (as 0,00). Reproducible: Always User Profile Reset: No Additional Info: Version: 6.4.2.2 Build ID: 4e471d8c02c9c90f512f7f9ead8875b57fcb1ec3 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.utf-8); UI-Language: en-US Calc: threaded
Created attachment 159552 [details] Test Split Database with HSQLDB 2.3.2 and Calc and Writer files: Decimal wrongly formatted as currency
On pc Debian x86-64 with LO Debian package, here what I tried: - launch Base - open a embedded HSQLDB file - create a new table with Design - field name : "test" - field type : "decimal" - Length : 4 - number of decimals : 2 - let default value empty by default => format example is disabled and displays "0" In brief, I don't reproduce this.
@ Julien: Yes, this is what I wrote: It's not happening with the embedded HSQLDB but with a split database.
Indeed, I read it too quickly.
Hello Hans, Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
The bug is still present in the recent version, I tested it with LibreOffice 7.2.2.2 .
The bug is still present for **split HSQLDB** database in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 7e3ddf1e5aae5e4e956495e3d86a8cbf6e251b5e CPU threads: 1; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Dear Hans, 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