Issue Description
I created an AdHoc View using MSSQL as a data source.
As it turned out, the result may change depending on the JDBC driver selected in setting data source.
For example, if a large value is entered in a Float type column, an error appears in the display result of the AdHocView.
Using the TIBCO JDBC driver seems to map MSSQL Float type to Java Float type and using Microsoft driver seems to map Float type to Double type.
Is this recognition correct?
Resolution
TIBCO MSSQL JDBC Driver uses a version of the DataDirect Progress MSSQL Drivers.
Per DataDirect Progress documentation, by default FLOAT database column type mapped to FLOAT Java type:
Default type mapping can be changed in WEB-INF/applicationContext-semanticLayer.xml config file, property:
<property name="jdbc2JavaTypeMapping">
In TIBCO JasperReports® Server v.6.4.0 the property contains mapping for Float type:
<entry key="FLOAT" value="java.lang.Float"/>
It can be changed to:
<entry key="FLOAT" value="java.lang.Double"/>
server restart required to apply the chnages.
As a result, newly created domain based on TIBCO MS SQL driver connection containes java.lang.Double type for Float MS SQL type.
Please note, you may need to re-save the existing domain to have them java.lang.Double type.
Solution tested with TIBCO JasperReports® Server v.6.4.0
Ref. Case 01552601
Recommended Comments
There are no comments to display.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now