Created attachment 174298 [details] Screenshot of unusable errormessage Open the attached screenshot. There is a query in the background. It is impossible to set the foreignkey in this query to a new value, because there are tow tables connected in the query. This is right behavior, but the error, which appears, gives: Error updating the current record /home/buildslave/source/libo-core/connectivity/source/commontools/dbtools.cxx:751 /home/buildslave/source/libo-core/dbaccess/source/core/api/OptimisticSet.cxx:181 Only the first paragraph has been shown in older LO-versions. Since Firebird has been introduced the two for normal users unusable informations will be shown also. That are informations for developer, not for users. If developer will need this informations, it should be shown pressing a button like "Details" (or something else).
Created attachment 174299 [details] Open the query, try to set Sport_ID = 1 where Sport_ID is 2. Look at the appearing error. This errormessage shows only Error updating the current record in LO 6.4.7.2 The new unusable errormessage first appears in LO 7.0.0.3 here. Tested with OpenSUSE 15.2 64bit rpm Linux.
Reproduced. I wouldn't call this a regression as we want to keep the info but just hide it behind some details button. Arch Linux 64-bit Version: 7.4.0.0.alpha1+ / LibreOffice Community Build ID: 47e8763114f12fe14e2a8dd94b5a339f614d23bc CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 20 May 2022
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
Behavior is still the same in LO 24.2.3.2 on OpenSUSE 15.6 64bit rpm Linux.