Description: I faced this problem when creating a table in design mode with multiple columns and different column types (more concretely, field lengths). Composite is made of multiple columns, with columns in between composite key members (composite key made of non-consecutive fields). If all fields are consecutive everything works as expected. The issue shows up in LO v6.4.6.2 (Linux), v6.4.7.2 (Windows 10, fresh install) and v7.0.3.1 (again, Windows 10 fresh install). Using Java 8 (251). All systems are 64 bits. Steps to Reproduce: 1. Create a new database. 2. Create a new table in design mode (do not save it). 3. Define a column (e.g. name it "col1", name does not matter) with VARCHAR type and length restricted to 9 characters. 4. Define another column (e.g. name it "col2", again, name does not matter) with SMALLINT type. 5. Define another column (e.g. name it "col3") with FLOAT type. 6. Define another column (e.g. name it "col4") with TINYINT type. 7. Select columns: col1, col2 and col4 (skipping col3), in that concrete order (when selecting them in reverse order, it works without issues). 8. Mark the 3 selected fields as primary key (composite key). 9. Check col1 length, it is 3, instead of 9. Actual Results: The length of col1 is 3, which matches the length of the last selected field. When selecting columns in reverse order it is 9 (because it picks the length of the latest selected column). Expected Results: The length of the first column should remain unchanged (9) after defining the composite key of the table. Reproducible: Always User Profile Reset: No Additional Info: Version: 6.4.7.2 (x64) Build ID: 639b8ac485750d5696d7590a72ef1b496725cfb5 CPU threads: 24; OS: Windows 10.0 Build 19041; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded
Created attachment 167313 [details] Short demo showing the bug
Have tested this one with internal HSQLDB and LO 7.0.3.1 on OpenSUSE 15.1 64bit rpm Linux. Could confirm the buggy behavior. The GUI will set the value for length from the last field of the chosen primary key fields. So if you want to get the right length you have to set the VARCHAR-field as last field in this group or you have to change the length after saving the table. Could be this is a bug inherited from OOo …
Dear algonzal, 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