| Summary: | Reportbuilder makes wrong SQL from queries | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Robert Großkopf <robert> |
| Component: | Base | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | detective.conan.1412, robert, serval2412 |
| Priority: | medium | ||
| Version: | 3.3.4 release | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: |
Open the report - wrong SQL appears. It isn't the SQL of the query.
screenshot of the report |
||
Created attachment 52885 [details]
screenshot of the report
I tried to reproduce the pb without success.
I'm on Debian pc x86-32 and I used the Debian packages 3.4.3.
Could you give your environment (Windows, Mac, Linux), the platform (x86-32, x86-64/AMD64, other ?) ?
With which version have you had this pb ? If not 3.4.3, could you please test again with 3.4.3 ?
My system: OpenSuSE 11.4, x86/32, LibreOffice 3.3.4
When trying to start the report it added (attachment 51880 [details]) it crashes: Wrong SQL ...
In version LibreOffice 3.4.x new bugs will appear. I will not change this system. My daugther has changed it to 3.4.2 on her laptop. Databases with a macro crashed - also with a SQL-error. This databases work on 3.3.4.
Robert
I have tested it with original LibreOffice 3.4.3 on OpenSuSE 11.4, 32 Bit. The report works without SQL-error. I have changed the version to 3.3.4 So if there's no error in 3.4.3 and it concerned only 3.3.4, we can say it this bug has been resolved/fixed. Great ! (In reply to comment #4) > So if there's no error in 3.4.3 and it concerned only 3.3.4, we can say it this > bug has been resolved/fixed. Great ! Please don't use FIXED if no known fix :) Setting as WORKSFORME. RESOLVED, FIXED or CLOSED bugs cant be KEYWORD NEEDINFO. |
Created attachment 51880 [details] Open the report - wrong SQL appears. It isn't the SQL of the query. A query is created for formatting and selecting one field. The query shows the correct field. When generating a report with this query (using it for grouping the report) the report would not start. It says: "column not found .... buchungen.Monat ...". There is no "buchungen"."Monat" in the query - only "Monat". So it could not be found. The wrong SQL-statement was created by the Report-Builder. If I switch the report not to analyse the SQL-code the report works well.