Created attachment 75979 [details] Two queries - one doesn't refresh the multiplication, the other does. Following query in the attached database don't refresh the field "sum", when a new input in "count" and "goods_ID" is made: SELECT "sale".*, "goods".*, "goods"."price" * "sale"."count" AS "sum" FROM "sale", "goods" WHERE "sale"."goods_ID" = "goods"."ID" All fields of "sale" and "goods" are shown, not the content of the multiplication-field "sum". This query works: SELECT "a".*, ( SELECT "price" * "a"."count" FROM "goods" WHERE "a"."goods_ID" = "ID" ) AS "sum" FROM "sale" AS "a" All fields of "sale" are shown, new values could be added and the "sum" is refreshed automatically in the correlated subquery. But this query doesn't work in LO 4.* - there isn't shown any content of a subquery, see bug https://bugs.freedesktop.org/show_bug.cgi?id=61166
Cannot reproduce with 4.0.2.0+ (my own development tree, which has some of my commits to 4.1 backported) Or maybe I didn't understand what you meant. Please post more detailed instructions. For me, both queries refresh correctly when I press the "refresh" button on the toolbar (a round arrow in antitrigonometric direction, that is the same direction as the hands of a watch). 1) I open both tables and both queries 2) I add lines to "sale" table (pay attention that the line is added only after the pencil at the left disappears) 3) I press refresh on both queries 4) they both have a new line The same with changing a line instead of adding one.
(In reply to comment #1) Hi Lionel, > > For me, both queries refresh correctly when I press the "refresh" button on > the toolbar (a round arrow in antitrigonometric direction, that is the same > direction as the hands of a watch). When you press the button it works. But when you move through the data by tab and with keys the field "sum" would not be refreshed when saving the data. > > 1) I open both tables and both queries > 2) I add lines to "sale" table (pay attention that the line is added only > after the pencil at the left disappears) > 3) I press refresh on both queries 3) I wouldn't do. I wanted to use this query for a form and will add data in a tablecontrol by keyboard and without mouse ... > 4) they both have a new line New line is right, but with tab saving by jumping to the next record the field "sum" will be empty.
(In reply to comment #2) > (In reply to comment #1) >> For me, both queries refresh correctly when I press the "refresh" button on >> the toolbar (a round arrow in antitrigonometric direction, that is the same >> direction as the hands of a watch). > When you press the button it works. But when you move through the data by > tab and with keys the field "sum" would not be refreshed when saving the > data. Still cannot reproduce, with LibreOffice 3.5.4.2 (Debian package). From the Query view, I change the "count" field, then press the down arrow (or tab as many times as necessary to go to next record/line). In both queries, the sum field of the line I just left is updated. Please give excruciatingly detailed reproduction steps.
Open query sum_no_sum_refresh. Input new "count", "goods_ID" (max. value 2). Go to next row with the arrow-keys or with tab. The field "sum" is empty - here with LO 3.5.*, 3.6.*, 4.0.* (all rpm-32bit) - also with win7, LO 3.6.*. The field shows 0 with LO 3.3.4. Open query sum_with_sum_refresh. Do the same. "sum" would filled in the field, when you enter the next new row. I will attach two screenshots of the queries - one without value in the field "sum", one of the other query.
Created attachment 76047 [details] Query without update in "sum" after enter a new row.
Created attachment 76048 [details] Query with update in "sum" after entering a new row.
OK, I get it now, reproduced.
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
Bug still exists with LO 5.1.0.3, OpenSUSE 42.1 Leap, 64bit rpm Linux.
Have tested this one with the first LO 3.3.0 - same bug. So I set the version to "Inherited FROM OOo"
** 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
Bug still exists with LO 5.3.1.1, OpenSUSE 42.1 Leap, 64bit rpm Linux.
** 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
Bug still exists with LO 6.0.2.1, OpenSUSE 42.3 Leap, 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 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 still present in Version: 6.3.3.2 Build ID: a64200df03143b798afd1ec74a12ab50359878ed Threads CPU : 8; OS : Mac OS X 10.14.6; UI Render : par défaut; VCL: osx; Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded
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
Bug still exists in LO 7.2.3.2 on OpenSUSE 15.2 64bit rpm Linux
Bug still exists in Version: 24.2.0.0.alpha1 (X86_64) / LibreOffice Community Build ID: 06946980c858649160c634007e5fac9a5aa81f38 CPU threads: 6; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded
Created attachment 191259 [details] Firebird embedded database It seems to be a specific problem with HSQLDB, I've tested with a Firebird database (converted from the original HSQL) and the problem is not shown, that is the field refresh adequately. Version: 7.6.3.2 (X86_64) / LibreOffice Community Build ID: 29d686fea9f6705b262d369fede658f824154cc0 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded
Also I think the sum_no_sum_refresh query is not entirely correct, because return two fields with the same name that are not particularized. May be it can be done in some databases but should be avoided.
(In reply to jcsanz from comment #23) > Also I think the sum_no_sum_refresh query is not entirely correct, because > return two fields with the same name that are not particularized. May be it > can be done in some databases but should be avoided. That is what GUI offers you. It won't work in direct SQL and won't work as view, but it will work with Base GUI.
I could reproduce the bug with the attached Firebird database. New row, '3' in field "count", '2' in field "goods_ID" and then down to next row. 2 bugs appear: Field "sum" will be empty and field "ID" (first "ID" from table "sale") will show '0' instead of '3'. So the field for AutoValue won't be refreshed. Think I have seen this before in a bug description.
It refresh correctly if you change some values in a existing field, so perhaps title should be change to reflects "on adding records"