Bug 494430 - Data Set Dialog shows wrong technical name for column
Summary: Data Set Dialog shows wrong technical name for column
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 4.5.0   Edit
Hardware: PC Windows 10
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Birt-DataAccess CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-24 11:02 EDT by Mark Mescher CLA
Modified: 2018-01-11 14:11 EST (History)
2 users (show)

See Also:


Attachments
Wrong value in column name (16.10 KB, image/png)
2016-05-24 11:02 EDT, Mark Mescher CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Mescher CLA 2016-05-24 11:02:06 EDT
Created attachment 261977 [details]
Wrong value in column name

Hi,
we updated our BIRT Version from 4.3 to 4.5.0.
Our custom ODA driver is working fine in 4.3.
When using it in 4.5.0, following problem occured.
When configuring the dataset, the Output Column tab of the dataset always shows the display name as the name of the column, not the technical name as it should.
We have prepared some example code and adjusted the ResultSetMetaData implementation for further explanation:

public String getColumnName(int index) throws OdaException {
	return "THIS IS THE NAME";
}

public String getColumnLabel(int index) throws OdaException {
	return "THIS IS THE LABEL"; 
}

As you can see in the attachment to this bug, in the Name column "THIS IS THE LABEL" is shown, but it should be "THIS IS THE NAME". Or does something in the API has changed between 4.3 and 4.5?

Thx

Mark
Comment 1 Matthias Braun CLA 2017-04-19 03:56:05 EDT
This problem also affects our custom ODA driver.
We cannot update from 4.4.2 to a newer version of BIRT.
Comment 2 Matthias Braun CLA 2018-01-11 14:11:15 EST
Is there any update, fix or workaround regarding this issue? 
Will it be fixed in 4.7.x or 4.8.0? 

We still cannot update from 4.4.2 to any higher version for 2 1/2 years now. This bug occurs since 4.5.0, which was released 2015-06-24.