Steps to reproduce (*) Download the soon-to-be-attached files smallspreadsheet.odt and constant_in_select_list.odb to the same directory on your system. (*) Open constant_in_select_list.odb in LibreOffice. Program presents windown constant_in_select_list.odb. (*) In Database pane click Queries, and in Queries pane right-click query_with_constants. Program presents pop-up menu. (*) In pop-up menu, select "Edit in SQL View...". Program presents SQL window showing statement SELECT "number", 'x', 12345, "word" FROM "Sheet1" (*) If the program does not already show a data grid, press <F5>. Program action actual: As shown in attached file query_window.png, the data grid shows the middle two columns blank. number 'x' 12345 word ------ --- ----- ---- 1 one 2 two 3 three Program action expected: The middle two columns should have non-blank (albeit very boring) values. number 'x' 12345 word ------ --- ----- ---- 1 x 12345 one 2 x 12345 two 3 x 12345 three I see this behaviour in LibreOffice version 3.3.4 (as delivered with ubuntu-natty), version 4.1.0.0.beta2, and in a couple of other fairly recent versions. I am leaving bug status UNCONFIRMED to encourage testing on other platforms.
Hey, where did status UNCONFIRMED go?
Created attachment 80736 [details] image of query result
Created attachment 80737 [details] a very small spreadsheet
Created attachment 80738 [details] database connecting to that spreadsheet
I an confirm it. My System: Linux 64bit rpm. LO 3.3.4 and LO 4.0.4.2 - both leave the two columns blank. If you set up such a query to the internal HSQLDB, it only works right, when you choose "direct SQL". In GUI-Mode the numbers weren't shown.
I still see the problem with my debug build of master commit 692878e, fetched 2014-08-13, built and running on debian-wheezy 64-bit.
Adding self to CC if not already on
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
The problem is still present daily dbgutil bibisect version 2016-01-18 running on debian-wheezy chroot'd to debian-sid.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
I still see the problem in daily Linux dbgutil bibisect repository version 2017-03-21 running on debian-stretch. Contrary to Robert's experience reported in comment 5, all the columns have data when I run my query by a double-click in the Queries pane.
** Please read this message in its entirety before responding ** 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
I still see the bug in daily Linux dbgutil bibisect repository version 2018-03-26 running on debian-sid.
I still see the bug in bibisect-linux-64.6.3 bibisect repository s-h 82463bdd from 2019-03-25.
