Problem of different Mysql connectors

[dianbo]

Hi,

I test Actuate V11 iServer Express recently, but some reports that work well in A10 sp1 can not work in V11. It is because of the differents connectors.

In A10 sp1, the mysql connector lib used is mysql-connector-java-com-3.1.10-bin.jar, but it is mysql-comm-5.1.7.jar for A11.

So for a simple sql statement "select user_id as id, user_name as name from user".
In A10 sp1, the output column names are id and name, and the display names are id and name too.
But in A11, the output column names are user_id and user_name, and the display names are id and name.

In old reports(work well in A10 sp1 iserver), dataSetRow["id"] and dataSetRow["name"] are used in text fields in a table or other items. But these will result in errors in A11 because there is no fields with names id and name.

So i can not move reports directly from A10 sp1 to A11. I have about 50 reports. Are there any suggestions about how to upgrade these reports?

Note: it is ok for jdbc:classicmodels:sampledb.

Best Regards & Thanks,

Dianbo

[averma]

Hi Dianbo,
Please feel free to report any issues for Actuate 11 BIRT products here(still in beta testing phase):
ED Main Page


Ashwini

[dianbo]

Originally Posted by averma

Hi Dianbo,
Please feel free to report any issues for Actuate 11 BIRT products here(still in beta testing phase):
ED Main Page


Ashwini

Hi Ashwini,

thanks for your response.
I have reported this issue in Redirecting to BIRT Exchange, but got a WONTFIX reply:
"This is caused by MySql driver's change of behavior. I guess you have also
changed your mySql driver when using those two version of BIRT. ..BIRT can do nothing for it ..."

The reason I posted the problem here is to ask for some help to resolve this issue smoothly.

Thanks,

Dianbo

[vdodson]

Hi dianbo, Have you tried replacing the newer JDBC driver with the older one? Otherwise, to make quicker work of the changes, you might jot down the fields from the Data Sets that use the 'as' operator... and use the XML Source view of the rptdesign file to quickly find/replace the values you need to change.

[garyxue]

Which Actuate11 build are you using? We have fixed the compatibility issue with BIRT reports running against Actuate MySQL driver in the M12 build (with a post 2009-12-07 build date).

As noted in Issue 96, there has been a change in MySQL driver from version 3.x to 5.x having to do with the names of aliased columns. See the following MySQL bugs for explanation of this change:
MySQL Bugs: #35610: Retrieving values by column label doesn't work
MySQL Bugs: #35150: Inconsistency in column name causes Hibernate to fail.

You will note the effect of this behavior change as you move from Actuate 10 to Actuate 11; however we have made sure that A10 BIRT reports continue to run without change in A11. If you continue to see report compatibility issues using M12 build or later, please report the problem here.