Description: When a SQL error -152 happens due a column long name, LO warns about the problem, but allows the user to proceed. Steps to Reproduce: 1. Open the attachment 2. Go to Reports 3. Try to open the Geschlecht_Diagramm 3.1. LO prompts about the Firebird migration 4. Proceed with the migration 4.1 LO warns about a SQL error -104: "Name linger than database column size caused by 'isc_dsql_prepare' " 5. Click on OK Actual Results: 1 - The following error is displayed on the terminal: https://gist.github.com/JoaoGFarias/84672ce2c4650d67b35499d86d9a6372 2 - The file opens anyway Expected Results: TBD - Not sure if the SQL error causes a problem in the migration process Reproducible: Always User Profile Reset: Yes Additional Info: Version: 6.3.0.0.alpha0+ Build ID: 16fffbe869785dffeda9ae0d9f7c18a6559a2093 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-01-19_01:39:11 Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded
Created attachment 148436 [details] Database attachment
Unconfirmed on mint 19.1 with Version: 6.3.0.0.alpha0+ Build ID: 16fffbe869785dffeda9ae0d9f7c18a6559a2093 CPU threads: 2; OS: Linux 4.15; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-01-19_01:39:11 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
Could confirm the behaviour. The view (named with more than 30 characters, see bug116987), isn't created. It is the problem of table-names, not of columns-names.
Also reproduced in Version: 6.1.0.0.alpha1+ Build ID: 3a801799536e6870f2fb111b1cc00b9575a35a39 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group
Still reproducible in Version: 6.4.0.0.alpha0+ Build ID: 7a0164f0d82d91e2ac481d74cdacfe9a7ad6080f CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded
Dear Joao Farias, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still reproducible with LO 7.1.5.1 on OpenSUSE 15.2 64bit rpm Linux.
Dear Joao Farias, 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
Bug still the same in LO 7.5.5.2 on OpenSUSE 15.4 64bit rpm Linux. File shouldn't be created. Reason for the error (Name of view has too much characters) should be shown. Then the user could solve this problem and try to migrate again.