The report builder with Firebird uses the original column names instead of aliases. So when you use an alias in a filter of a report, it would not know it. This breaks the behavior known from HSQLDB.
Using Ubuntu 18.04 w/ Libo 6.1 Beta2 I can't replicate your problem. I create a view with column aliases and when I create a RB report against it the field picker displays the column aliases, sorting and grouping displays the column aliases and the sidebar property editor for fields does the same. @Gerhard, do you have an example file you can share with the problem?
In the attached example, the field picker shows the alias. When you select it, it will enter the original name of the view he current view is based upon.
Created attachment 142915 [details] Sample DB
Created attachment 142941 [details] screen shot showing issue Got it: Two QueryDefinitions; MitgliederVerbandExcelvorlage and Abfrage1. MitgliederVerbandExcelvorlage uses table MitgliederVerband Abfrage1 uses MitgliederVerbandExcelvorlage and creates one alias, VereinID Report is based on Abfrage1 and in the set filter dialog references Abfrage1.VereinID But the filter SQL snippet references "MitgliederVerbandExcelvorlage"."Verien" instead of ( "Abfrage1"."VereinID" = '0' ) As far as I can tell it doesn't change the result set (didn't after I added some records and ran the report with both variations), but it seems it should the later and the not the former. Put it all in pictures(why not? ;) see attachment
Changing summary to more closely match error
Created attachment 142942 [details] hsql version of file Very same behavior with hsql based file (had to change the queries just a tad but otherwise identical DBs) So, not just firebird, will update summary again.
There is an essential difference between HSQLDB and Firebird. The HSQLDB version accepts a filter like ( "VereinsID" = 0 ) The Firebird version does not. I created this ticket mainly because, that the Report Builder would not accept aliases in the filter and even pop up an error.
Dear Gerhard Schaber, 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
Dear Gerhard Schaber, 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
It is the same with Version: 7.2.4.1 (x64) / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-AT (de_AT); UI: de-DE Calc: threaded
In 7.2.7.2, I get the error message when using the alias in the report filter: 1. Edit Bericht1 report 2. In Data tab, Filter field, use: ( "MitgliederVerbandExcelvorlage"."VereinsID" = '0' ) 3. Save and close, open the report Result: firebird sdbc_report error: *Dynamic SQL Error *SQL Error code =-206 *Column unknown Using the filter dialog to change the field value works for other fields, but selecting the alias in the list does not. Same in recent master build: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 42364fbfafaa95773c073cc080142b64ec1786fb CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Andreas, given that you fixed bug 132924, what do you think?
Confirmed in: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b3b926e32d81ff3bd6e065b986221382530c79a5 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-AU (de_DE); UI: en-US Calc: CL threaded I will check why it uses the wrong table alias.