Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 342623

Summary: Non descriptive error message when previewing results in the Dataset Editor
Product: z_Archived Reporter: Michael <mike.loughran>
Component: BIRTAssignee: Xiaoxiao Wu <xwu>
Status: CLOSED WONTFIX QA Contact: Xiaoying Gu <bluesoldier>
Severity: major    
Priority: P3 CC: bluesoldier, mike.loughran, mwu, xwu
Version: unspecified   
Target Milestone: 3.7.0   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Michael CLA 2011-04-12 14:28:43 EDT 
Build Identifier: 2.6.1.v20100915-1750

Hello All,

I have a user who has reported the following issue to me:  

When he attempted to preview the results while in the Dataset Editor, he is receiving an error.  With the previous version that he used, if the error was related to a bad sql statement entered, he would receive the pop up error window and it would list the Oracle/SQL Error: 

(:Cannot get the result set metadata.
SQL statement does not return a ResultSet object.
SQL error #1: ORA-00933: SQL command not properly ended)

Since the upgrade from 2.3.0 to 2.6.1, no errors have been returned except for the message: "Error happened while running the report."  Clicking on the Details button displays a stack error, with the Oracle error buried down in it.  

I have located the following bug - 304463 - which appears to be the same issue, just at a different point.

Please let me know if I can provide any additional details or files.  This is my first posting, so I know I might be missing something.

Thanks,
mike


Reproducible: Always

Steps to Reproduce:
1.  Create a bad sql query, one that you know will generate an error - in the Dataset Editor
2. Click on "Preview results"
3.  Note the error generated/displayed
Comment 1 Xiaoxiao Wu CLA 2011-04-26 05:01:09 EDT 
Hi Mike,

Would you please provide a sample report design for me to clearly indentify the phenomenon you described？

In addition, I'd suggest you use the latest 2.6.2 build to have another try to make sure whether the problem still exists now.

Thanks,
Xiaoxiao
Comment 2 Xiaoxiao Wu CLA 2011-05-16 06:09:54 EDT 
Hi Mike,

For the issue you submitted, we think that might be the expected behavior.

Since we cannot decide the length of the error message, it might be very long and ugly to display. Instead of showing the detailed error message, we just display a short error message with the detailed information in the drop-down message box, in which all the error cause/information you wanted could be found.

So I think the current behavior might be reasonable and expected as most users want.

Thanks,
Xiaoxiao
Comment 3 Xiaoxiao Wu CLA 2011-07-06 02:12:49 EDT 
Hi Mike,

Since it is not supposed to resolve the issue you mentioned, I'll close this bug later. Please feel free to reopen the bug if you have some additional opinions.

Now mark this bug as WONTFIX.

Thanks,
Xiaoxiao