Created attachment 146363 [details] Screenshot: Where to choose definition of a table while importing ... See bug 121208 for start. First step of the dialog of the table import wizard show the possibility to import only the definition of a table. Choose this option. Go to the next steps. At the end press "Create". No table will be created. This doesen't work with a table with field names and content and doesen't wor also with a table only created with field names. This bug happens with LO 6.1.3.2 64bit rpm Linux.
Confirmed using Ubuntu 18.04 and 6.1.3.2 rel. For this one use case of a calc import (though a table form Writer might do the same, I wouldn't be surprised) First what worked for definition only: Using drag and drop from Source -> Target hsql(emb) hsql(emb) hsql(emb) fb(emb) fb(emb) hsql(emb) Then what failed for definition only: Calc(rows) hsql(emb) Calc(rows) fb(emb)
also I changed the summary to start with IMPORT:
Confirmed the same behavior in LO 5.4.7 and AOo 4.1.6RC
Setting the severity back to normal, also.
I submitted a patch on gerrit https://gerrit.libreoffice.org/#/c/63250/
Created attachment 146538 [details] bt with debug symbols from ODatabaseExport::executeWizard
Patch was wrong, can't help here->uncc myself.
Dear Robert Großkopf, 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 http://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 is the same in LO 6.3.3.2 on OpenSUSE 15.1 64bit rpm Linux
Dear Robert Großkopf, 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
Still the same in LO 7.2.3.2 on OpenSUSE 15.2 64bit rpm Linux.
This bug is still present in: Version: 7.3.0.3 (x64) / LibreOffice Community Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL
Same behaviour in LOo 7.3.1.1 paralel in Windows10 in a firebird not embeded database trying to import from a calc sheet, but also from a HSQLDB 2.4 splitted database.
Sorry, I have to correct myself. I had used other version. Now with LOO 7.3.1.1 seems to be working, except if the data source is a calc sheet. In this case the structure is not copied. Windows 10, Version: 7.3.1.1 (x64) / LibreOffice Community Build ID: 349cd3ad57dce98d6b54b76f8e9f456ac7d7edb7 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL
Still the same buggy behavior in LO 24.2.0.3 on OpenSUSE 15.4 64bit rpm Linux.