Bug 65047 - No report generation when sorting order with old Report-Engine
Summary: No report generation when sorting order with old Report-Engine
Status: RESOLVED DUPLICATE of bug 64985
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
4.0.0.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 64917 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-05-27 18:13 UTC by Juan J. Magaña
Modified: 2013-06-29 19:15 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Sample Database (33.53 KB, application/vnd.oasis.opendocument.database)
2013-06-29 17:00 UTC, Juan J. Magaña 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Juan J. Magaña 2013-05-27 18:13:48 UTC 
I'm using Ubuntu 12.04 precise (amd64) and the Libreoffice 4.0 ppa. However, the bug that I have encountered also takes place with the official deb packages from www.libreoffice.org.

Every time I generate a report that is sorted alphabetically or in any way, I always get this:

24-may-2013 14:09:18 com.sun.star.wizards.db.DBMetaData$CommandObject <init>
GRAVE: null
com.sun.star.uno.RuntimeException: [jni_uno bridge error] Java calling UNO method getByName: [map_to_uno():string] null-ref given!
java stack trace:
 at com.sun.star.bridges.jni_uno.JNI_proxy.dispatch_call(Native Method)
 at com.sun.star.bridges.jni_uno.JNI_proxy.invoke(JNI_proxy.java:183)
 at com.sun.proxy.$Proxy17.getByName(Unknown Source)
 at com.sun.star.wizards.db.DBMetaData$CommandObject.<init>(DBMetaData.java:305)
 at com.sun.star.wizards.db.DBMetaData.getCommandByName(DBMetaData.java:272)
 at com.sun.star.wizards.db.DBMetaData.getTableByName(DBMetaData.java:251)
 at com.sun.star.wizards.db.CommandMetaData.getColumnObjectByFieldName(CommandMetaData.java:146)
 at com.sun.star.wizards.db.SQLQueryComposer.appendSortingCriterion(SQLQueryComposer.java:182)
 at com.sun.star.wizards.db.SQLQueryComposer.prependSortingCriteria(SQLQueryComposer.java:158)
 at com.sun.star.wizards.db.SQLQueryComposer.prependSortingCriteria(SQLQueryComposer.java:149)
 at com.sun.star.wizards.report.ReportTextImplementation.reconnectToDatabase(ReportTextImplementation.java:286)
 at com.sun.star.wizards.report.Dataimport.importReportData(Dataimport.java:196)
 at com.sun.star.wizards.report.Dataimport.createReport(Dataimport.java:212)
 at com.sun.star.wizards.report.CallReportWizard$ReportWizardImplementation.trigger(CallReportWizard.java:104)

 at com.sun.star.bridges.jni_uno.JNI_proxy.dispatch_call(Native Method)
 at com.sun.star.bridges.jni_uno.JNI_proxy.invoke(JNI_proxy.java:183)
 at com.sun.proxy.$Proxy17.getByName(Unknown Source)
 at com.sun.star.wizards.db.DBMetaData$CommandObject.<init>(DBMetaData.java:305)
 at com.sun.star.wizards.db.DBMetaData.getCommandByName(DBMetaData.java:272)
 at com.sun.star.wizards.db.DBMetaData.getTableByName(DBMetaData.java:251)
 at com.sun.star.wizards.db.CommandMetaData.getColumnObjectByFieldName(CommandMetaData.java:146)
 at com.sun.star.wizards.db.SQLQueryComposer.appendSortingCriterion(SQLQueryComposer.java:182)
 at com.sun.star.wizards.db.SQLQueryComposer.prependSortingCriteria(SQLQueryComposer.java:158)
 at com.sun.star.wizards.db.SQLQueryComposer.prependSortingCriteria(SQLQueryComposer.java:149)
 at com.sun.star.wizards.report.ReportTextImplementation.reconnectToDatabase(ReportTextImplementation.java:286)
 at com.sun.star.wizards.report.Dataimport.importReportData(Dataimport.java:196)
 at com.sun.star.wizards.report.Dataimport.createReport(Dataimport.java:212)
 at com.sun.star.wizards.report.CallReportWizard$ReportWizardImplementation.trigger(CallReportWizard.java:104)
java.lang.NullPointerException
 at com.sun.star.wizards.db.CommandMetaData.getColumnObjectByFieldName(CommandMetaData.java:147)
 at com.sun.star.wizards.db.SQLQueryComposer.appendSortingCriterion(SQLQueryComposer.java:182)
 at com.sun.star.wizards.db.SQLQueryComposer.prependSortingCriteria(SQLQueryComposer.java:158)
 at com.sun.star.wizards.db.SQLQueryComposer.prependSortingCriteria(SQLQueryComposer.java:149)
 at com.sun.star.wizards.report.ReportTextImplementation.reconnectToDatabase(ReportTextImplementation.java:286)
 at com.sun.star.wizards.report.Dataimport.importReportData(Dataimport.java:196)
 at com.sun.star.wizards.report.Dataimport.createReport(Dataimport.java:212)
 at com.sun.star.wizards.report.CallReportWizard$ReportWizardImplementation.trigger(CallReportWizard.java:104)
24-may-2013 14:09:18 com.sun.star.wizards.report.ReportTextImplementation reconnectToDatabase
GRAVE: null
com.sun.star.sdbc.SQLException: La columna no es válida.
 at com.sun.star.bridges.jni_uno.JNI_proxy.dispatch_call(Native Method)
 at com.sun.star.bridges.jni_uno.JNI_proxy.invoke(JNI_proxy.java:183)
 at com.sun.proxy.$Proxy63.appendOrderByColumn(Unknown Source)
 at com.sun.star.wizards.db.SQLQueryComposer.appendSortingCriterion(SQLQueryComposer.java:186)
 at com.sun.star.wizards.db.SQLQueryComposer.prependSortingCriteria(SQLQueryComposer.java:158)
 at com.sun.star.wizards.db.SQLQueryComposer.prependSortingCriteria(SQLQueryComposer.java:149)
 at com.sun.star.wizards.report.ReportTextImplementation.reconnectToDatabase(ReportTextImplementation.java:286)
 at com.sun.star.wizards.report.Dataimport.importReportData(Dataimport.java:196)
 at com.sun.star.wizards.report.Dataimport.createReport(Dataimport.java:212)
 at com.sun.star.wizards.report.CallReportWizard$ReportWizardImplementation.trigger(CallReportWizard.java:104)

No problem whatsoever with Libreoffice 3.6 or lower versions. If there is no sorting option, then there is no problem either.
Comment 1 Robert Großkopf 2013-05-29 20:17:27 UTC 
Do you use the Report-Builder or the elder wizard, which only appers, when the report-builder isn't installed?
Here is a link how a report of the old report-engine looks like:
https://bugs.freedesktop.org/attachment.cgi?id=79792
Comment 2 Juan J. Magaña 2013-05-29 20:36:12 UTC 
Hi Robert, I'm not using the report builder extension, if that's what you mean. I'm using the old report engine.
Comment 3 Robert Großkopf 2013-05-30 06:39:38 UTC 
(In reply to comment #2)
> Hi Robert, I'm not using the report builder extension, if that's what you
> mean. I'm using the old report engine.

Most people doesn't know, that this old engine is already there. The report-builder-extension is mostly direct installed with the packages of LO. I have first heard about the old engine by Ubuntu-users, when we discussed problems with reports in Base and recognized, that we are not writing about the same software.

What java-version do you use? Could be a problem with java 7 ...
Comment 4 Juan J. Magaña 2013-05-30 08:07:07 UTC 
Hi again, Robert. Actually I've tried different versions of Java. Currently I'm using  1.6.0_45. I've tried with OpenJDK, Java 7 and lower Java 6 versions. I always get the same mistake no matter which Java version I use. I'm no expert, but it seems to be connected with the uno package. I don't know, it's just a guess.
Comment 5 Robert Großkopf 2013-05-30 09:22:13 UTC 
Seams to be the same reason as reported in https://bugs.freedesktop.org/show_bug.cgi?id=64985
But with OpenSuSE 12.3 32bit rpm there appears no error-message. The report would be opened with the default content, not the content of the table. So I can only confirm bug 64985. I can't confirm the errormessage and won't mark this as a duplicate.
Comment 6 Clemens Wallner 2013-06-03 09:13:23 UTC 
*** Bug 64917 has been marked as a duplicate of this bug. ***
Comment 7 Juan J. Magaña 2013-06-18 15:38:22 UTC 
Same story on version 4.1.0 beta2 downloaded from libreffice.org and testing different Java versions. I assume that this bug could be marked as new.
Comment 8 Thomas Hackert 2013-06-22 07:12:42 UTC 
Hello Juan, *,
when did you get this messages? When you start LO from commandline? Or is there a window, which opens with your mentioned messages? And would you be so kind to test it with 4.1.0.0.RC1 as well, please? Maybe it is fixed there ... ;)
Sorry for the inconvenience
Thomas.
Comment 9 Juan J. Magaña 2013-06-23 07:32:11 UTC 
Hi Thomas, I can see the bug info when I start LO from the command line. Otherwise, you cannot see anything, simply it doesn't generate the report. Following your advice, I've tried it with 4.1.0.0.RC1 but no luck so far. Thanks for your interest.
Comment 10 Thomas Hackert 2013-06-26 05:57:52 UTC 
Hello Juan, *,
(In reply to comment #9)
> Hi Thomas, I can see the bug info when I start LO from the command line.
> Otherwise, you cannot see anything, simply it doesn't generate the report.
> Following your advice, I've tried it with 4.1.0.0.RC1 but no luck so far.
> Thanks for your interest.

would you be so kind to attach a test document to this bug, please? I have not one handy to test it ... :(
TIA
Thomas.
Comment 11 Juan J. Magaña 2013-06-29 17:00:50 UTC 
Created attachment 81695 [details]
Sample Database

Hi Thomas, this is a sample database. Starting the database with "libreoffice --base LoansDatabase.odb" will give you the error.
Comment 12 Robert Großkopf 2013-06-29 17:31:26 UTC 
Isn't this a duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=64985 ? What is the difference? Do you get the error-message when starting the report? With my system I get a report with the default-content. No error-message.
Comment 13 Juan J. Magaña 2013-06-29 17:59:38 UTC 
It's probably the same error, I agree. I had this happening a long time before I reported it because I couldn't find any bug fitting this description. 

If you don't open the database from the terminal, you get absolutely no error message, you get simply 'dummy data' as Tyler says. I tried to debug it a bit by starting from the terminal, trying to find the reason why this happened.
Comment 14 Robert Großkopf 2013-06-29 19:15:28 UTC 
So let mark us this as a duplikate.

*** This bug has been marked as a duplicate of bug 64985 ***